Loading SEO Dispatch

Loading page

AI assistant access (MCP)

Connect your AI assistant with a site token

Connect AI tools like Cursor or Claude to one site in SEO Dispatch using the Model Context Protocol (MCP). Each token is scoped to exactly one site. There is no one-click Connect in those clients today.

One token per site

MCP access is granted per site. A token created for one property belongs strictly to that property and cannot read, list, or update data for any other property or workspace. If a tool call specifies a different property ID, the server rejects it with a forbidden error.

What a site token can do

Read open fixes, Guides, and site context for that specific site.
Update fix statuses (such as in progress or applied) for that site.
Save article drafts and verify live fixes for that site.

What it cannot do

Access, list, or modify any other site in your workspace.
Write directly to your website codebase, Git repository, or CMS.
Access billing information, user passwords, or OAuth tokens.

Connect your AI assistant

Open your site in SEO Dispatch and select the Settings tab.
Scroll to the AI assistant access (MCP) section.
Click Generate new site token, enter the required Token name, select the permissions your assistant needs, and click Generate token.
Copy the generated token immediately. It is shown only once and stored as a secure hash.
Configure your client using the server URL https://seodispatch.app/api/mcp and pass your token as the bearer authorization token.

Configuration for Cursor and Claude

Add the SEO Dispatch MCP server configuration to your AI client. Replace YOUR_SITE_TOKEN with the site token generated in Settings.

Cursor configuration

Add this to your project .cursor/mcp.json or global Cursor MCP settings:

{
  "mcpServers": {
    "seo-dispatch": {
      "url": "https://seodispatch.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SITE_TOKEN"
      }
    }
  }
}

Claude Desktop configuration

Add this to your claude_desktop_config.json file:

{
  "mcpServers": {
    "seo-dispatch": {
      "url": "https://seodispatch.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SITE_TOKEN"
      }
    }
  }
}

Give your AI assistant a safe setup brief

If your assistant configures connections automatically, give it this brief:

Connect to SEO Dispatch using the remote MCP endpoint https://seodispatch.app/api/mcp. Do not ask me to share my SEO Dispatch password, MFA code, browser cookies, session tokens, or personal credentials. Prefer the official Connect flow for Cursor or Claude Desktop when available. Otherwise authenticate using the site-scoped bearer token provided. All operations must target only the authorized site.

This is a generic MCP configuration brief, not a compatibility guarantee for any third-party client.

Clients

Cursor: paste a site token
Claude Desktop: paste a site token
Claude Code: paste a site token
Windsurf: paste a site token

Publishing and CMS paste handoff

SEO Dispatch does not push articles or code to your CMS or website repository. When an AI assistant prepares an article through MCP, the server saves the article draft and returns the complete text for you to paste into your CMS.

The handoff is simple: copy the draft content returned by the assistant and paste it into your CMS. Once published and live on your domain, you can verify the URL through SEO Dispatch or have your assistant verify it via MCP.

Revoking a site token

You can revoke access anytime. For a site token: open that site's Settings → AI assistant access (MCP), find the token, and click Revoke. For Connect: open account Settings → Connected AI tools and revoke that client.

Revocation takes effect immediately. A revoked token or Connect grant is rejected on the next request. Revoking one path does not remove the other.

You control what ships

MCP provides structured data and fix guidance to the AI assistant you configure. SEO Dispatch does not review code written by your AI assistant or publish it to the web. Inspect proposed changes, test thoroughly, and maintain proper backups.

You remain responsible for any instructions given to AI assistants, changes made to your codebase, and content published to your site. You can always copy or download a saved Guide instead of connecting an AI assistant.

For full legal terms and privacy details, see our Terms of Service and Privacy Policy.