8. AI access (MCP)

AI assistants such as Claude can read your SEO data through the Model Context Protocol (MCP). You can then ask questions like "Which pages lost clicks this month?" or "Where is seedsman.com ahead of us?".

Access is read-only: an assistant can never change or delete anything. Pro and Agency editions include it.

Create a token

Go to Integrations → AI access → New token. Owners and admins can do this.
Enter a name, for example "Claude Desktop".
Choose the data it may read (projects, search performance, keywords, rankings, competitors, opportunities).
Choose all projects or only some.
Choose an expiry (30, 90 or 365 days, or never).

The token (scc_…) is shown once. Copy it into your AI client right away. You can revoke tokens at any time on the same page.

Connect your AI client

Server URL: https://seo.example.com/mcp
Authentication: header Authorization: Bearer scc_…
Transport: Streamable HTTP

Claude Code (terminal):

claude mcp add --transport http seo-control-center https://seo.example.com/mcp --header "Authorization: Bearer scc_YOUR_TOKEN"

Other MCP clients: add a remote (HTTP) MCP server with the URL and header above.

What the assistant can use

Tool	Answers
`projects_list`	Which projects exist
`search_performance_summary`	Clicks, impressions, CTR and position with the change against the previous period
`search_queries_list`, `search_pages_list`	Top queries and pages
`keywords_list`	Tracked keywords with metrics
`rankings_summary`, `keyword_history`	Positions, visibility, winners and losers, and one keyword's history
`competitors_list`, `competitor_compare`	Competitor visibility, gaps and who is ahead
`opportunities_list`	Open opportunities with their data

Safety

Every call is logged in the audit log (tool, project, result), never with its content.
A token acts for the user who created it. It stops working when that user loses access.
Limit: 60 requests per minute per token.
Treat a token like a password. If one leaks, revoke it and create a new one.