MCP Studio API

Everything you can do in the MCP Studio dashboard, you can do over HTTP: create an MCP server from a list of sources, choose its tools, add and remove sources, build custom tools, write retrieval rules, refresh it when content changes, read its analytics, and delete it.

It is the same API the n8n integration is built on, so anything a workflow does, your own code can do too.

Audience	Developers automating MCP servers from scripts, CI pipelines, internal tools, or their own products
Prerequisites	An MCP Studio account and an API key

Base URL

https://appatools.com/mcp-studio

Every path in this reference is relative to it. Requests and responses are JSON unless a page says otherwise.

Quickstart

Create an API key under Account > API Keys, then export it:

export MCP_STUDIO_API_KEY="msk_live_..."

1. Create a server. It returns right away with the endpoint URL, while its sources index in the background.

curl -X POST https://appatools.com/mcp-studio/api/mcp/create \
  -H "Authorization: Bearer $MCP_STUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Engineering Context",
    "sources": [
      { "url": "https://docs.example.com" },
      { "url": "https://github.com/example/api" }
    ],
    "tools": ["search_docs", "get_code_examples", "ask_question"]
  }'

{
  "serverId": "cm1x2y3z40001abcd",
  "slug": "engineering-context-a1b2",
  "url": "https://appatools.com/mcp-studio/api/mcp/engineering-context-a1b2",
  "configSnippet": "{ \"mcpServers\": { ... } }",
  "visibility": "public",
  "accessToken": null
}

2. Wait for indexing. Poll the server until every source reports complete. Large sites take a few minutes.

curl https://appatools.com/mcp-studio/api/mcp/engineering-context-a1b2 \
  -H "Authorization: Bearer $MCP_STUDIO_API_KEY"

3. Connect an AI client. Paste configSnippet into Cursor, Claude Desktop, or Windsurf, or call the endpoint yourself.

Try it in the browser

Every reference page has an interactive console. Open an operation, select Test Request, paste your API key under Authentication, and send a real request to MCP Studio from this page. Your key goes from your browser straight to MCP Studio and is not stored here.

Requests made from the console act on your real account. Use a key scoped to a test server if you want to explore without touching anything else.

Reference

Resource	What it covers
Servers	Create, list, get, refresh, make private, delete
Sources	Add and remove sources, rotate an MCP source's credential
Tools	Choose which built-in and custom tools a server exposes
Custom tools	Build a tool from a plain-English description
Retrieval rules	Tell a server when a source matters
Analytics	Usage summary and the request log
Account	Plan, usage, and entitlements
MCP endpoint	The JSON-RPC endpoint AI clients connect to

OpenAPI documents

Every page is rendered from an OpenAPI 3.1 document you can download, import into Postman or Insomnia, or feed to a code generator.

mcp-studio-api.yaml: every operation in one document
One document per resource, linked at the bottom of each reference page

Next steps

Authentication: API keys, scoped keys, and private server tokens
Errors and limits: error format, plan limits, and rate limits
n8n integration: the same operations as no-code workflow steps

Base URL​

Quickstart​

Try it in the browser​

Reference​

OpenAPI documents​

Next steps​