MCP Server
Setup
Ask your AI assistant for SEO data directly: the SEORCH MCP server connects Claude, Cursor and other Model Context Protocol (MCP) clients to all SEORCH APIs, from search volume and rankings to the SEO check. All you need is an API key. What the server can do and how to get access is explained on the SEO MCP Server page.
Server URL: https://seorch.net/api/mcp/
Send the key in the X-API-Key: YOUR_KEY or Authorization: Bearer YOUR_KEY header or, if your client does not support headers, as ?key=YOUR_KEY in the URL. The server uses stateless Streamable HTTP.
Claude Code: Run this once in your terminal:
claude mcp add --transport http seorch https://seorch.net/api/mcp/ --header "X-API-Key: YOUR_KEY"
Clients with a JSON configuration (e.g. mcp.json) add the server like this:
{
"mcpServers": {
"seorch": {
"type": "http",
"url": "https://seorch.net/api/mcp/",
"headers": {
"X-API-Key": "YOUR_KEY"
}
}
}
}
Claude (web and desktop): go to Settings → Connectors, add a custom connector and enter the URL with your key: https://seorch.net/api/mcp/?key=YOUR_KEY.
Then just ask things like “What is the search volume of patio furniture in the US, and when should my guide be online?” or “Where does my site rank for pizza delivery in Chicago?”
Tools
There is one tool per API. The arguments match the parameters of the API; see its documentation for details. A key only sees the tools of the APIs it is enabled for.
| Tool | API | What for |
|---|---|---|
get_search_volume | Search Volume API | Search volume, CPC, competition, trend and seasonality for up to 500 keywords |
get_search_volume_forecast | Search Volume Forecast API | 12-month forecast with range, seasonality and publish-by date |
get_keyword_ideas | Keyword Tool API | Related keywords for up to 10 keywords or a URL |
get_suggest_keywords | Suggest API | Autocomplete keywords from 14 sources, optionally with search volume |
get_questions | Questions API | Question keywords for a keyword |
get_google_rankings | Ranking API | Google results, also local and mobile, with your position |
seo_check | SEO Check API | SEO check of a URL, optionally only selected areas |
get_core_web_vitals | Chrome UX Report API | Core Web Vitals from real user data for up to 10 URLs |
compare_source | Source Comparison API | Differences between two user agents, e.g. Googlebot and Chrome |
check_hreflang | Hreflang API | Hreflang check of a page or XML sitemap |
create_content_briefing | Content Briefing API | Targets for a text based on the top results |
Response
Each tool returns the response of its API as JSON text and as structured data (structuredContent). Example get_search_volume:
| Field | Meaning |
|---|---|
results | For each keyword search_volume, cpc, cpc_high, cpc_low, competition (0 to 100), yoy (change vs. last year in percent), seasonal_peak and monthly |
skipped | Keywords with special characters or over 55 characters that the service cannot query |
{
"country": "de",
"months": 12,
"results": [
{
"keyword": "gartenmöbel",
"search_volume": 110000,
"cpc": 0.86,
"cpc_high": 1.02,
"cpc_low": 0.21,
"competition": 100,
"yoy": -14,
"seasonal_peak": "2026-03",
"monthly": {
"2025-11": 27100,
"2025-12": 22200,
"2026-01": 49500,
"2026-02": 110000,
"2026-03": 246000,
"2026-04": 201000,
"2026-05": 201000,
"2026-06": 135000,
"2026-07": 110000,
"2026-08": 90500,
"2026-09": 49500,
"2026-10": 33100
}
}
],
"skipped": [
"was?"
]
}
Errors
Without a valid key the server responds with HTTP 401 (JSON-RPC error -32001); if the key is not enabled for any API, with 403 (-32003). Errors during a tool call are returned as a tool result with isError: true and the same error code as the API, such as invalid_country, rate_limited or endpoint_not_allowed, so the assistant can react.
Limits
The same limits as for the APIs apply: 10 requests per minute and 500 per day per key, each tool call counts once. Daily or monthly limits of a single API, such as the Ranking API, also apply to its tool.