Loading page
Loading page
Model Context Protocol Integration
Generate a site token in SEO Dispatch, then paste it into Cursor, Claude Desktop, Claude Code, or Windsurf. There is no Connect button in those clients today.
One site per connection. Pro features are on the waitlist. No credit card required.
Why connect an SEO MCP server
Raw AI models have no access to your search performance, existing content library, or published HTML. SEO Dispatch gives your agent verified site context.
Your assistant can query real clicks, impressions, and average positions so it works from demand on your site, not a generic checklist.
Before drafting, your agent can check topic overlap against pages you already have and your confirmed business focus, so new pages do not fight your own rankings.
After you paste changes into your CMS, your agent can check the published URL and confirm title, meta description, or schema is live before you close the fix.
Workflow Preview
After you paste a site token into your AI client, your agent can read open fixes, draft markup for your CMS, and check the published page after you paste.
assistant call mcp:list_fixes { propertyId: "prop_harbor", status: "new", severity: "high" }
Found 2 high-severity fixes backed by 4.2k monthly Search Console impressions:
1. /portfolio/ missing meta description (est. 180 clicks/mo opportunity)
2. /services canonical points to outdated http scheme
assistant call mcp:get_fix_detail { opportunityId: "opp_meta_portfolio" }
Paste this meta description into the CMS page settings:
"Explore award-winning branding, web design, and digital product case studies by Harbor Studio in Melbourne."
Once it is saved in the CMS, I will run live verification on https://harborstudio.example/portfolio/.
assistant call mcp:verify_fix_live { opportunityId: "opp_meta_portfolio" }
Verified live HTTP 200: Meta description tag detected and matches target. Ready to mark Applied.
Tool Capabilities
Sessions only get the tools allowed by that site token and server write mode. Read tools are safe to query. Status updates and live checks need Fix Management permission and write mode.
Read tools use this site token. Status updates and live checks need Fix Management permission and server write mode.
list_fixesSite ReadQueries SEO fixes for a property with filters for status, category, severity, and URL. Available with this site token.
get_fix_detailSite ReadReads technical rationale, code diffs, Search Console metrics, and crawler evidence for one fix. Available with this site token.
list_open_fixesSite ReadQueries new and in progress fixes without changing lifecycle state. Available with this site token.
get_fix_contextSite ReadReads concise implementation context and evidence summary for one fix.
update_fix_statusManage Fixes + Write ModeTransitions a fix to in progress or applied with a mandatory explanation.
batch_update_fix_statusManage Fixes + Write ModeAtomically updates up to 25 fixes in one call with idempotency protection.
verify_fix_liveManage Fixes + Write ModeRuns SSRF protected HTTP checks against the published page to verify title, meta, canonical, or JSON-LD tags. Does not mark the fix applied automatically.
Client config
Open that site in SEO Dispatch, go to Settings, and open AI assistant access (MCP). Generate a site token, copy it once, then paste the config below into your client.
{
"mcpServers": {
"seo-dispatch": {
"url": "https://seodispatch.app/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_SITE_TOKEN"
}
}
}
}Replace YOUR_SITE_TOKEN with the site token from Settings → AI assistant access (MCP).
Join the waitlist. When access opens, create one site token in that site's Settings and paste it into Cursor or Claude.
Free account checks available. Pro features currently on waitlist.