MCP server for Google Search Console (Search Analytics, read-only)
Seo MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for Google Search Console (Search Analytics, read-only).
Семь универсальных stdio MCP-серверов для SEO: доступ к SERP, Wordstat, Google Search Console, Яндекс.Вебмастеру, Яндекс.Метрике и self-hosted A-Parser прямо из Claude Code (и любого MCP-клиента). Все инструменты read-only, вывод — строгий JSON. К конкретному сайту не привязаны: дефолты (свойство GSC, хост Вебмастера, счётчик Метрики) настраиваются на лету.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Seo is connected, these are the calls the assistant has available:
xmlstock — xmlstock_serp, xmlstock_images, xmlstock_news, xmlstock_video, xmlstock_wordstat, xmlstock_wordstat_dynamics, xmlstock_wordstat_regionsxmlriver — xmlriver_serp, xmlriver_images, xmlriver_news, xmlriver_check_index, xmlriver_suggest, xmlriver_related_questions, xmlriver_balancewordstat — wordstat_frequency, wordstat_dynamics, wordstat_regions, wordstat_regions_treegsc — gsc_query, gsc_inspect_url, gsc_list_sites, gsc_get_site, gsc_list_sitemaps, gsc_get_sitemapywm — ywm_hosts, ywm_summary, ywm_search_queries, ywm_queries_history, ywm_recommended_queries, ywm_popular, ywm_indexing_history, ywm_sqi_historymetrika — metrika_report, metrika_bytime, metrika_counters, metrika_goals, metrika_traffic_sources, metrika_geo, metrika_devices, metrika_landing_behavioraparser — aparser_ping, aparser_status, aparser_proxies, aparser_parsers, aparser_parser_fields, aparser_get_preset, aparser_serp_google, aparser_serp_yandexYou will need 8 environment variables: XMLSTOCK_USER, XMLSTOCK_KEY, WORDSTAT_FOLDER_ID, WORDSTAT_API_KEY, YWM_HOST_ID, METRIKA_COUNTER_ID, YANDEX_OAUTH_TOKEN, APARSER_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Seo's toolset — xmlstock, xmlriver, wordstat and 4 more — is a fair guide to whether it matches your workflow. It is maintained by antohins; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Seo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| xmlstock | xmlstock_serp, xmlstock_images, xmlstock_news, xmlstock_video, xmlstock_wordstat, xmlstock_wordstat_dynamics, xmlstock_wordstat_regions, xmlstock_wordstat_regions_tree, xmlstock_balance |
| xmlriver | xmlriver_serp, xmlriver_images, xmlriver_news, xmlriver_check_index, xmlriver_suggest, xmlriver_related_questions, xmlriver_balance |
| wordstat | wordstat_frequency, wordstat_dynamics, wordstat_regions, wordstat_regions_tree |
| gsc | gsc_query, gsc_inspect_url, gsc_list_sites, gsc_get_site, gsc_list_sitemaps, gsc_get_sitemap |
| ywm | ywm_hosts, ywm_summary, ywm_search_queries, ywm_queries_history, ywm_recommended_queries, ywm_popular, ywm_indexing_history, ywm_sqi_history, ywm_external_links, ywm_broken_links, ywm_diagnostics, ywm_important_urls, ywm |
| metrika | metrika_report, metrika_bytime, metrika_counters, metrika_goals, metrika_traffic_sources, metrika_geo, metrika_devices, metrika_landing_behavior, metrika_search_phrases, metrika_top_landings |
| aparser | aparser_ping, aparser_status, aparser_proxies, aparser_parsers, aparser_parser_fields, aparser_get_preset, aparser_serp_google, aparser_serp_yandex, aparser_suggest, aparser_request, aparser_bulk_request |
{
"mcpServers": {
"gsc-seo": {
"command": "npx",
"args": ["-y", "seo-tools-mcp-xmlstock"],
"env": {
"XMLSTOCK_USER": "your-value",
"XMLSTOCK_KEY": "your-value",
"WORDSTAT_FOLDER_ID": "your-value",
"WORDSTAT_API_KEY": "your-value",
"YWM_HOST_ID": "your-value",
"METRIKA_COUNTER_ID": "your-value",
"YANDEX_OAUTH_TOKEN": "your-value",
"APARSER_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| XMLSTOCK_USER | Configuration value read at startup. | Optional |
| XMLSTOCK_KEY | Credential the server authenticates with. | Yes |
| WORDSTAT_FOLDER_ID | Configuration value read at startup. | Optional |
| WORDSTAT_API_KEY | Credential the server authenticates with. | Yes |
| YWM_HOST_ID | Endpoint or connection string the server talks to. | Optional |
| METRIKA_COUNTER_ID | Configuration value read at startup. | Optional |
| YANDEX_OAUTH_TOKEN | Credential the server authenticates with. | Yes |
| APARSER_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.