Each local area page used to take us half a day to create and optimize.
With SEOmatic, we can create hundreds of pages in the same time, which helps our clients make the best use of their budget.
It's transformed how we deliver scalable SEO solutions.
Will Hawkins
Marketing Director, Digi-Business UK
Agents read your Search Console data, do the work, and prove what actually moved. You decide what ships.
14-Day Free Trial. $1 card check, refunded. Cancel Anytime.
A hosted Model Context Protocol server that exposes SEOmatic's tools to any MCP client. Connect interactively over OAuth 2.1, or with a workspace API key as a Bearer token. Tools are consolidated into a small set of outcome tools, each annotated read-only or acting.
| Field | Value |
|---|---|
| Endpoint | https://app.seomatic.ai/api/mcp |
| Transport | Streamable HTTP (stateless, POST JSON-RPC 2.0) |
| Protocol | 2025-06-18 (2025-03-26 and 2026-07-28 also accepted) |
| Server | seomatic v1.0.0 |
| Auth | OAuth 2.1 (interactive clients) or Authorization: Bearer smk_live_... |
For clients that support a custom connector by URL, such as Claude and Claude Code, just give them the endpoint and let them run OAuth. The server publishes standard discovery documents, so the client finds the authorization server, opens a browser for you to sign in and pick a workspace, and stores the token itself. No API key to paste.
URL: https://app.seomatic.ai/api/mcp Auth: OAuth (the client discovers it automatically)
Discovery follows the MCP spec: the endpoint returns 401 with a WWW-Authenticate pointing at /.well-known/oauth-protected-resource (RFC 9728), whose authorization server metadata lives at /.well-known/oauth-authorization-server (RFC 8414). PKCE (S256) is required; tokens are bound to this resource. Dynamic client registration and client-id metadata documents are both supported.
For headless agents and clients that take a static token, mint a workspace API key and send it as a Bearer token. This is also how the Claude Messages API connector authenticates, via its authorization_token field.
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"headers": { "Authorization": "Bearer smk_live_..." }
}
}
}| Method | What it does |
|---|---|
initialize | Negotiate the protocol version and get serverInfo. |
tools/list | The scope-filtered tool roster this key can call. |
tools/call | Invoke a tool. Failures return as an isError result, not a transport error, so the agent can react. |
The tools/listroster is filtered to the key's scopes, so a client only ever sees tools it can actually call.
| Scope | Lane | Tools it unlocks |
|---|---|---|
read:gsc | Free | Direct Search Console reads. |
chat:ask | Free | All insight tools: GSC, keywords, backlinks, SERP, analytics, ads, Business Profile, datasets, templates. |
agents:act | Paid | The acting tools: SEO tasks, campaigns, bulk edits, blog authoring, skills. Works on any paid plan over MCP. |
Acting over MCP works on any paid plan; the same acting tools over the REST API require Infrastructure.
Over MCP the full surface is grouped into a small set of outcome tools (for example gsc_performance, keyword_research, campaign_manage), each taking an action that selects the operation. Every tool carries MCP annotations, so a client knows at a glance whether it only reads (readOnlyHint) or can stage a change. Nothing is destructive by default: acting tools stage proposals a human approves. The complete fine-grained tool list, with each input schema, is in the REST reference.