MCP server Claude CodeCodexCursor +2
MCP server for Yandex Wiki with read/write tools and readonly mode. Runs locally from the mcp-yandex-wiki Python package.
24 tagged yandex, measured the same way as everything else here.
Browse within: model-context-protocol 20seo 18search-console 16
MCP server Claude CodeCodexCursor +2
MCP server for Yandex Wiki with read/write tools and readonly mode. Runs locally from the mcp-yandex-wiki Python package.
MCP server Claude CodeCodexCursor +2
One of 8 in server.json
Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only). Runs locally from the seo-tools-mcp-aparser npm package. Needs 6 environment variables to run.
MCP server Claude CodeCodexCursor +2
MCP server for Yandex Metrika analytics. Runs locally from the ya-metrics-mcp Python package.
MCP server Claude CodeCodexCursor +2
MCP server for XMLRiver — Google/Yandex SERP parsing and Wordstat frequency data via XML API. Runs locally from the xmlriver-mcp Python package.
expremiental/yandex-metrika-mcp
MCP server Claude CodeCodexCursor +2
Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language. Remote server at mcp.getaiaiai.ru.
MCP server Claude CodeCodexCursor +2
MCP server "yandex-wordstat-mcp" as configured in N1arko/yandex-wordstat-mcp. Runs locally from the yandex-wordstat-mcp Python package.
johnisanerd/Apify-Yandex-Search-Scraper
MCP server Claude CodeCodexCursor +2
Yandex search results, images, and SERP data via the Apify Yandex Search Scraper, hosted MCP. Remote server at mcp.apify.com.
denis-samatov/yandex-workspace-mcp
MCP server Claude CodeCodexCursor +2
MCP server "yandex-workspace-mcp" as configured in denis-samatov/yandex-workspace-mcp. Runs locally from the yandex-workspace-mcp Python package.
MCP server Claude CodeCodexCursor +2
A locally run MCP server for Yandex 360 services, including Yandex Wiki. It gives AI assistants access to tools for those services.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: