Call authorized SEO tools with MCP
Stateless MCP JSON-RPC over HTTP POST. Use a workspace service-account API key or a delegated MCP application credential. Legacy keys with the read scope retain read-only access; SEO mutation and execution tools additionally require seo:write and seo:run respectively. A delegated credential selecting more than one workspace must send its permitted public workspace ID in x-workspace-id. The tool catalogue is scope-filtered. Tool refusals can return an MCP result with isError=true. Paid execution remains disabled until native SEO allowances and spending policies are configured; ordinary AI answer credits cannot fund it. OpenSEO AI visibility is unwired. No long-lived GET stream or DELETE session operation is supported.
Authorizations
A workspace API key. Data endpoints require a service-account key with the specified scopes.
Headers
Permitted public workspace ID for delegated credentials with multiple authorized workspaces. An API key retains its own workspace boundary.
A stable request identity for a safely retried tool invocation. Reuse the same identity and arguments after an uncertain response.
The MCP transport requires support for both response media types.
"application/json, text/event-stream"