Skip to main content
The MCP server is currently in beta. Tools and response shapes are subject to change.
The Hado SEO MCP server lets AI agents — Claude, Claude Code, Cursor, Codex, and any other Model Context Protocol client — work with your account the same way the REST API does: read crawl analytics, export raw logs, and manage cache rules, blocked paths, and routing rules.
Because every MCP tool runs through the same API layer as the dashboard and REST endpoints, an agent can’t do anything your API key couldn’t do with plain HTTP — the same validation, plan limits, domain permissions, and rate limits apply.

​
What agents can do

Analyze crawl activity

Daily crawl rollups per bot, page-level crawl counts, AI referral traffic, and raw per-request crawl logs

Manage caching

List, create, update, and delete per-path cache rules; purge and re-render pages on demand

Control crawl access

Block paths from prerendering, with optional noindex/nofollow robots directives

Manage routing

Create, update, and delete redirects and proxy rules on your live domain
See MCP Tools for the full list of the 19 tools and their parameters, and MCP Setup to connect a client.

​
Definitions

​
Authentication

The server authenticates with the same API keys as the REST API, sent as a header when you connect the client:
The MCP server is available on every plan. Plans differ by monthly call quota — see Plan Limits.
Every tool call counts as one API request against your key’s rate limits (60 requests/minute, plus your plan’s monthly quota — from 300 calls/month on Starter up to 12,000 on Agency). Failed calls are not charged.

​
Key scopes

API keys carry scopes that limit what connected agents can do: Keys have both scopes by default. For agents, create a read-only key unless you specifically want the agent changing configuration — MCP keys end up in agent config files, which are easy to leak.

​
Safety notes

Write tools change your live domain within seconds. Routing rules in particular affect real visitor traffic, not just bots. Give agents a read-only key by default, and when you do grant write, review what the agent plans to change before approving tool calls.
Every write made through the MCP server is recorded in an audit log — the tool used, its arguments, the API key, and the outcome — so changes made by agents are always traceable. If something looks wrong, contact support and we can tell you exactly what changed and when.