Connect over MCP

AskEditor’s MCP connector is hosted at https://mcp.askeditor.com (Streamable HTTP, OAuth 2.1). It is the only supported MCP route: there is no npm package to install. You don’t need an API key. An unauthenticated request to the server returns 401 with an RFC 9728 WWW-Authenticate challenge, so a compliant MCP client discovers the OAuth flow and runs it automatically: you authorize in a browser window, approve the scopes, and the agent acts as you, on your credits. Clients register themselves via Dynamic Client Registration; PKCE (S256) and refresh tokens are supported.

Endpoints

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://api.askeditor.com/.well-known/oauth-authorization-server`
Dynamic Client Registration (RFC 7591)	`https://api.askeditor.com/oauth/register`

Claude Code
claude.ai / Claude Desktop
Cursor

claude mcp add askeditor --transport http https://mcp.askeditor.com

Settings → Connectors → Add custom connector → https://mcp.askeditor.com → Authorize with your AskEditor account.

Add an MCP server with URL https://mcp.askeditor.com and complete the OAuth flow in the browser window that opens.

Once authorized, the agent can list templates, estimate, upload material, run jobs, and fetch results: see Tools. Troubleshooting: if the connector won’t connect, re-authorize from your client’s connector settings; tool lists are cached by some clients, so reconnect after we announce new tools.

Overview

Setting up

Core concepts

Agents & MCP

Endpoints

​Endpoints

Endpoints