The MCP server lets an AI agent — Claude, Cursor, Claude Code — connect directly to your PilotScribe account and do everything you can do in the app, from a prompt: add and configure a site, pull keywords, capture your proprietary facts, generate and publish articles, connect a domain or CMS, and wire the blog into your own codebase.

It exposes the full action surface over one authenticated connection — the same operations the in-app assistant runs, always scoped to your own account. It's the fastest path for developers and the ideal fit for agencies setting up many client sites. Only wiring published articles into a site? That still works too — see the Content API.

Endpoint & auth

URL — https://app.pilotscribe.com/mcp
Auth — OAuth. The first time your agent connects, a browser opens to sign in to PilotScribe (the same email / Google login as the app). No keys to copy by hand.

Connect — Claude Code

# Claude Code — add the remote server, then authenticate
claude mcp add --transport http pilotscribe https://app.pilotscribe.com/mcp
# then, inside Claude Code:
/mcp            # opens the browser to sign in to PilotScribe (OAuth)

Connect — Cursor

// ~/.cursor/mcp.json (or .cursor/mcp.json in your project)
{
  "mcpServers": {
    "pilotscribe": {
      "url": "https://app.pilotscribe.com/mcp"
    }
  }
}

Claude Desktop & claude.ai: add a custom connector and paste the same URL. Any MCP client that supports remote servers + OAuth works.

What the agent can do

The MCP exposes the full set of account actions — the same ones the in-app assistant uses. The essentials:

Set up a site — add it by URL (auto-analyzed), confirm the business profile, pull a relevant keyword shortlist
Ground the writing — capture your own facts, numbers and point of view (the knowledge interview) so articles aren't just a rehash of page 1
Create content — generate a full article or a free teaser, or turn a YouTube video into one
Publish anywhere — a custom domain we host, a CMS connector (WordPress, Shopify, Webflow, Ghost, HubSpot, Wix), or a webhook
Wire a coded site — mint the read-only Content API key, get ready-to-paste code for your framework, and verify it renders after you deploy
Track performance — Search Console traffic, backlinks, and the autopilot's content plan

Everything is scoped to your own account over OAuth — an agent can only ever touch your data, never anyone else's. Tools that change or remove data are labelled [destructive] in their description (for example deleting an article or removing a domain), so a well-behaved client confirms with you before calling them.

Try it

Once connected, just ask:

"Use PilotScribe to set up SEO for this site end-to-end:
 add it, confirm the profile, pull keywords, write the first article,
 then wire the blog into my Next.js app and verify it after I deploy."

No MCP? Point any LLM at the docs

Agents without MCP can still self-serve from machine-readable docs:

pilotscribe.com/llms.txt — a compact integration brief
pilotscribe.com/openapi.json — the OpenAPI 3.1 spec

Stuck? Ask the in-app assistant, or email contact@pilotscribe.com.