Guide · SEO agent, AI & ML
MCP access
Connect Claude or MCP Inspector to the SEO tools, choose scopes and revoke access.
Overview
Two MCP servers expose the platform to AI assistants. The admin server needs OAuth 2.1 with PKCE; the public server is read-only and serves published articles only, without sign-in. Each has a kill switch (ADMIN_MCP_ENABLED, PUBLIC_MCP_ENABLED) and the page shows whether it is on.
To connect Claude: in Claude, Settings → Connectors → Add custom connector with the admin server URL shown on the page. Claude registers itself, sends you to a consent page on this site, and then appears under Connected clients.
- seo:read: read SEO metrics, keyword opportunities, the review queue, draft diffs, audit issues, flow runs and LLM usage.
- seo:flows: start drafting, sync, audit and report flows (drafts still wait for your approval on the site).
- seo:review:reject: reject drafts and add review notes.
No scope can approve, publish, roll back or submit to search engines. Connected clients shows each client's scopes, who allowed it and when it was last used; Revoke ends its access at once.
Diagram
Where to find it
This page of the admin: /admin/automation/mcp. Only admins (and read-only demo accounts) can open it.
Settings on this page
What each setting does and its default. Defaults only: the manual never shows the values saved on a site.
MCP servers and scopes
No scope can approve, publish, roll back or submit to search engines.
| Setting | What it does | Default |
|---|---|---|
| Admin server | OAuth 2.1 with PKCE; switch ADMIN_MCP_ENABLED. | off |
| Public server | Read-only, published articles only, no sign-in; switch PUBLIC_MCP_ENABLED. | off |
| Scope seo:readseo:read | Read SEO metrics, keyword opportunities, the review queue, draft diffs, audit issues, flow runs and LLM usage | — |
| Scope seo:flowsseo:flows | Start drafting, sync, audit and report flows (drafts still wait for your approval on the site) | — |
| Scope seo:review:rejectseo:review:reject | Reject drafts and add review notes | — |
| Connected clients | Each client with its scopes, who allowed it, when it was last used and its status; Revoke ends its access at once. | — |