> ## Documentation Index
> Fetch the complete documentation index at: https://askeditor.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect over MCP

> The hosted connector: one address, sign in with OAuth, and your agent edits your AskEditor projects.

AskEditor's MCP connector is hosted at **`https://mcp.askeditor.com/mcp`**
(Streamable HTTP, OAuth 2.1). It is the only supported MCP route: there is
no npm package to install.

Once connected, your agent works on your AskEditor projects with the same
tools the editor's own assistant uses: it opens a project, cuts and trims,
adds text, captions and graphics, looks at the edit, and exports it. Every
change appears live in the editor. See [MCP tools](https://askeditor.com/docs/mcp/tools.md).

## The AskEditor plugin for Claude and ChatGPT

If you use the Claude desktop app or the ChatGPT desktop app, install the
AskEditor plugin instead of adding the connector by hand. It connects this
same server and opens the editor beside the chat, so you watch every edit as
it is made. The install steps live on the plugin pages:

* **Claude**: [askeditor.com/claude-code-plugin](https://askeditor.com/claude-code-plugin)
* **ChatGPT**: [askeditor.com/chatgpt-plugin](https://askeditor.com/chatgpt-plugin)

## Add the connector to any MCP client

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --transport http askeditor https://mcp.askeditor.com/mcp
> ```
>
> Then sign in, which is a separate step: run `/mcp`, pick **askeditor**
> and choose **Authenticate**. Adding the server does not sign you in.

> [tab] claude.ai / Claude Desktop
>
> Settings → Connectors → **Add custom connector** →
> `https://mcp.askeditor.com/mcp` → approve it on the AskEditor page that
> opens.

> [tab] Cursor and others
>
> Add an MCP server of type HTTP (some clients call it a remote or
> streamable HTTP server) with the address
> `https://mcp.askeditor.com/mcp`, then approve it on the AskEditor page
> your client opens.

> [!WARNING]
>
> **Connected is not signed in.** Most clients report the server as connected
> the moment you add the address. If you see no AskEditor tools, or only a pair
> named `authenticate` and `complete_authentication`, you have not approved it
> yet. Those two are placeholders your client shows; they are not AskEditor's.

## Signing in

**You don't need an API key.** A request without a token returns `401` with
an RFC 9728 `WWW-Authenticate` challenge, so a compliant client discovers the
OAuth flow and runs it: an AskEditor page names the app and the account it
will use, and you press **Allow**. The agent then acts as you, on your
credits. Clients register themselves with Dynamic Client Registration; they
are public clients, with PKCE (`S256`) and refresh tokens.

| What | URL |
| - | - |
| MCP server | `https://mcp.askeditor.com/mcp` |
| Protected resource metadata (RFC 9728) | `https://mcp.askeditor.com/.well-known/oauth-protected-resource` |
| Authorization server metadata (RFC 8414) | `https://mcp.askeditor.com/.well-known/oauth-authorization-server` |
| Authorization | `https://mcp.askeditor.com/oauth/authorize` |
| Token | `https://mcp.askeditor.com/oauth/token` |
| Dynamic Client Registration (RFC 7591) | `https://mcp.askeditor.com/oauth/register` |

The only scope is `mcp`. A client that cannot run OAuth can send an API key
instead, as `Authorization: Bearer <key>`; make one under **Settings → API
keys** in AskEditor.

## Approvals and credits

Editing is free. Paid work (generated video, pictures, voices and music, and
AskEditor's own transcription the first time a file is heard) uses your
AskEditor credits. A call that costs more than a few credits, or deletes
something, waits for you: in your client's approval dialog, or on a card in
the editor, after which the agent calls again with the `approval_id` it was
given. Prices are on [askeditor.com/pricing](https://askeditor.com/pricing).

## Disconnecting

Disconnect an app from the **MCP** page in your AskEditor workspace, or
revoke its key under **Settings → API keys**. It stops working straight away.

## Troubleshooting

* **No tools, or only `authenticate`**: you have not approved the app yet.
  Run the sign-in step for your client.
* **New tools are missing**: clients load the tool list when a session
  starts. Start a new session, or reconnect.
* **The connector won't connect**: re-authorize from your client's connector
  settings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.