Appa Tools documentation for MCP Studio, including setup, guides, concepts, and API-related reference content.

Skip to main content

Headless Context MCP

Headless Context MCP is an MCP server for building MCP servers. Connect it to Claude, Cursor, Codex, or any MCP client, and you can create Context MCP Studio servers, add sources, check indexing, change tools, write retrieval rules, and read analytics by asking for it in a chat. You never open the wizard.

"Make me an MCP server from https://docs.stripe.com and our GitHub repo, make it private, and tell me when it has finished indexing."

Your assistant turns that into the right calls, shows you the results, and gives you the new server's endpoint to connect.

DetailValue
Endpointhttps://appatools.com/mcp-studio/api/headless/mcp
TransportStreamable HTTP (POST)
AuthenticationAuthorization: Bearer msk_live_..., an MCP Studio API key
Tools21, covering servers, sources, tools, custom tools, retrieval rules, analytics, and your plan

How it relates to the MCP Studio API​

Headless Context MCP is the MCP Studio API spoken as MCP. Each tool makes the same request you would make with curl, under the same key, so everything the API enforces applies here too: plan limits, a key's server scope, rate limits, and validation. If you already use the API, you already know what each tool can do; the tools reference lists the endpoint behind each one.

Use the API when your own code is in charge, for example provisioning a server for every new customer. Use Headless Context MCP when a person is in charge and would rather ask than click.

Get started​

  1. Create an API key in Account > API Keys. Set Used from to Direct. To let the assistant touch only some servers, limit the key to those servers.
  2. Add the endpoint to your client with the key in the Authorization header. Connect your client has the exact configuration for each client.
  3. Ask your assistant to list your MCP Studio servers. If it answers with your servers, you are connected.

What it will not do​

A few things stay in MCP Studio on purpose:

  • Sources that need an API key. A key typed into a chat ends up in a transcript, so credentialed sources are added in the dashboard.
  • File uploads. Upload files in the wizard, then manage the server from your assistant.
  • Billing and account deletion. Both move money or cannot be undone, and both have their own page in MCP Studio.

Deleting a server, a source, a custom tool, or a retrieval rule always requires the assistant to confirm with you first. See Security and limits.