> ## Documentation Index > Fetch the complete documentation index at: https://chatobserver.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # 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. ## OpenAPI ````yaml POST /api/seo/mcp openapi: 3.1.1 info: title: chatobserver public API version: '2026-09-09' description: >- Track AI visibility, manage prompts, inspect collected answers and citations, and integrate workspace data with your own tools. Visibility endpoints use workspace API keys. Data endpoints use scoped service-account keys; spreadsheet client endpoints use authorised client sessions. See the authentication guide for each credential type. contact: name: chatobserver support url: https://chatobserver.com/contact email: support@chatobserver.com servers: - url: https://app.chatobserver.com description: Production API security: - WorkspaceKey: [] - BearerKey: [] tags: - name: Workspace description: Validate access and list the workspace project and available platforms. - name: Prompts description: Create, schedule, organise, activate and retrieve tracked prompts. - name: Answers description: Retrieve collected AI answers, their analysis and visibility trends. - name: Brands description: Manage brands and compare their visibility in AI answers. - name: Sources and citations description: Analyse cited domains, pages and ownership across answers. - name: Visitor analytics description: Read website visitor and crawler analytics for the workspace. - name: Content opportunities description: Retrieve content-gap findings and recommendations for tracked prompts. - name: Usage description: Read workspace consumption and allowance summaries. - name: Data connections description: Discover authorised connections, source accounts and connector catalogues. - name: Data queries description: >- Create versioned queries, publish definitions and inspect integration contracts. - name: Data operations description: >- Execute, validate, cancel and inspect operations and page through result rows. - name: Data delivery description: Manage schedules, transfers, destinations and import workflows. - name: Data definitions description: Manage reusable definitions and their immutable versions. - name: Data webhooks description: >- Configure event delivery, inspect deliveries, replay events and rotate secrets. - name: Client authorisation description: Authorise spreadsheet clients using a user-approved challenge exchange. - name: Spreadsheet clients description: >- Access document-bound client sessions, queries, schedules, bindings and write claims. - name: AI visibility audits description: Create website visibility audits and retrieve their report links. - name: Version 1 description: Integrate with the version 1 visibility and analytics endpoints. - name: Tracked coverage description: >- Track published coverage, maintain its metadata and inspect exact-page citation evidence with the same workspace feature access as the dashboard. - name: Reports description: >- Discover accessible native reports and assess exact saved revisions using measured, context-specific evidence. - name: SEO description: >- Use authorized workspace SEO tools through the stateless MCP endpoint. Availability follows native workspace access and rollout controls; paid tools require a separately configured SEO allowance and spending admission. OpenSEO AI visibility tools remain unavailable. paths: /api/seo/mcp: post: tags: - SEO summary: Call authorized SEO tools with MCP description: >- 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. operationId: postSeoMcp parameters: - name: x-workspace-id in: header required: false description: >- Permitted public workspace ID for delegated credentials with multiple authorized workspaces. An API key retains its own workspace boundary. schema: type: string - name: idempotency-key in: header required: false description: >- A stable request identity for a safely retried tool invocation. Reuse the same identity and arguments after an uncertain response. schema: type: string format: uuid - name: Accept in: header required: true description: The MCP transport requires support for both response media types. schema: type: string example: application/json, text/event-stream requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SeoMcpRequest' responses: '200': description: >- MCP JSON-RPC result or protocol error; inspect tool result isError before using its content. content: application/json: schema: $ref: '#/components/schemas/SeoMcpResponse' '202': description: Accepted MCP notification; no response body. '400': description: >- Invalid request, unsupported protocol input, or a body exceeding the 1 MiB limit. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' '401': description: Authentication required. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' '403': description: Workspace, origin, scope or rollout access denied. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' '406': description: The MCP transport cannot satisfy the requested response media type. '415': description: Unsupported request media type. '429': description: Rate limit exceeded. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' '500': description: A safe internal error response. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' '503': description: Required service or access authority unavailable. content: application/json: schema: anyOf: - $ref: '#/components/schemas/SeoHttpError' - $ref: '#/components/schemas/SeoMcpResponse' security: - WorkspaceKey: [] - BearerKey: [] - McpConnection: [] components: schemas: SeoMcpRequest: type: object required: - jsonrpc - method properties: jsonrpc: type: string const: '2.0' id: anyOf: - type: string - type: number method: type: string description: An MCP JSON-RPC request or notification method. params: type: object additionalProperties: true additionalProperties: false SeoMcpResponse: type: object required: - jsonrpc - id properties: jsonrpc: type: string const: '2.0' id: anyOf: - type: string - type: number - type: 'null' result: {} error: type: object required: - code - message properties: code: type: integer message: type: string data: {} additionalProperties: false oneOf: - required: - result - required: - error additionalProperties: false SeoHttpError: type: object required: - error properties: error: anyOf: - type: string - type: object required: - code properties: code: type: string additionalProperties: false additionalProperties: false securitySchemes: WorkspaceKey: type: apiKey in: header name: x-chatobserver-key description: >- A workspace API key. Data endpoints require a service-account key with the specified scopes. BearerKey: type: http scheme: bearer description: The workspace or service-account API key as a bearer token. McpConnection: type: http scheme: bearer description: >- Delegated application credential issued after Chatobserver account consent. Restricted to selected workspaces and explicitly supported MCP operations. The MCP server access token is a separate credential and cannot be used here. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.