Popcorn Editor
Documentation AI agents (MCP)

AI agents (MCP)

Connect other clients

Last updated Aug 23, 2026

Any client that speaks MCP over streamable HTTP can connect to Popcorn Editor. The endpoint is your app origin plus /mcp/popcorn, and your exact URL is shown in the app under Settings → Your agent access, where you also mint the agent token these clients send as a bearer header. The examples below use https://popcorneditor.com/mcp/popcorn as a placeholder.

Use an agent token for editors and CLIs. Browser sign-in works for app-style connectors like Claude and ChatGPT, which come back to a known web address. Desktop editors normally complete OAuth through a private handler on your own machine instead, and that path is not available here yet. Mint a token under Settings → Your agent access, choose Read & write or Read only, and paste it as an Authorization header. See Where you can connect for the full picture.

Cursor

Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json to make it available globally):

{
  "mcpServers": {
    "popcorn": {
      "url": "https://popcorneditor.com/mcp/popcorn",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Replace <token> with an agent token from Settings → Your agent access. The token is shown once when you create it, so paste it right away.

VS Code (Copilot agent mode)

Add the server to .vscode/mcp.json:

{
  "servers": {
    "popcorn": {
      "type": "http",
      "url": "https://popcorneditor.com/mcp/popcorn",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Or let VS Code write that file for you: open the command palette and run MCP: Add Server, which can save the server either to the current project or to your user profile so it is available in every project.

Copilot's agent mode picks up the server and can call the Popcorn tools (get-schema, validate-design, create-design, render-design, list-templates and the rest, listed in the tools reference).

Any MCP client

A client can connect if it supports:

  • Streamable HTTP transport to https://popcorneditor.com/mcp/popcorn, and
  • either custom request headers, so it can send Authorization: Bearer <token> with an agent token, or OAuth 2.1 with a web redirect (the server supports dynamic client registration, so leave any Client ID/Secret fields blank and authorize in the browser).

Connector-style UIs (Claude on web, desktop and mobile, and ChatGPT) use OAuth. See Connect Claude and Connect ChatGPT. CLIs and IDEs use agent tokens, like Gemini CLI and the examples above.

Stdio-only clients

If a client only supports stdio servers (no remote HTTP), bridge it with mcp-remote. Configure the client to run:

npx mcp-remote https://popcorneditor.com/mcp/popcorn --header "Authorization: Bearer <token>"

The bridge runs locally as a stdio server and forwards everything to Popcorn over HTTP.

Limits and revocation

Requests are rate-limited to 60 per minute per user, and every call is workspace-scoped and permission-checked server-side. To target a team workspace instead of your personal one, send an optional X-Workspace header with the workspace uuid.

For token scopes (Read & write vs Read only), expiry options, and how to revoke access, see Tokens & security. For what a connected agent can and cannot touch, see Is it safe?.

All results →