Google Webtools MCP vs Yandex Webmaster MCP
A side-by-side look at the Google Webtools MCP and Yandex Webmaster MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Google Webtools MCPMarketingGoogle Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.51GoodAuth: oauth 2.0Verdict: choose Google Webtools MCP for marketing work; choose Yandex Webmaster MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
GChoose Google Webtools MCP when
- You need dedicated capabilities in the Marketing domain.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_APPLICATION_CREDENTIALS. - You want tools like
list_properties, get_property_details, add_property.
Choose Yandex Webmaster MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YANDEX_WEBMASTER_TOKEN, YANDEX_OAUTH_CLIENT_ID, YANDEX_OAUTH_CLIENT_SECRET. - You want tools like
login, submit_code, get_hosts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Google Webtools MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 51/100 · Good | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_APPLICATION_CREDENTIALS | YANDEX_WEBMASTER_TOKENYANDEX_OAUTH_CLIENT_IDYANDEX_OAUTH_CLIENT_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 39 | 10 |
| Full listing | View Google Webtools MCP | View Yandex Webmaster MCP |
Tools & capabilities
Google Webtools MCP tools 39
list_propertiesStarting point — see every GSC property you can access and your permission level on each.get_property_detailsCheck the type and permission level of one specific property.add_propertyRegister a new site in Search Console (verification is a separate step).delete_propertyDrop a property from the authenticated account's Search Console site list. Historical data is not destroyed — the property can be added back.list_sitemapsSee which sitemaps are submitted and whether Google reports errors or warnings.get_sitemap_detailsDrill into one sitemap: URL counts by content type, last download time, error and warning counts.submit_sitemapSubmit a new sitemap after publishing or moving one.delete_sitemapWithdraw a sitemap that is stale, duplicated, or returning errors.get_search_analyticsThe raw query — full control over dimensions, filters, search type, row limit, data state, aggregation. Use when the shaped tools below don't fit.get_performance_summary"How are we doing?" — clicks, impressions, CTR, position with period-over-period comparison. Trend advice is withheld when the previous period returned no data at all.compare_periodsCompare two explicit date ranges side by side (before/after a release, seasonal comparison).get_top_queriesTop queries by clicks, each scored against the CTR benchmark for its position.- +27 more on the listing page
Yandex Webmaster MCP tools 10
loginSign in to Yandex from here. Opens your browser to approve access; the code returns automatically over a local redirect, so this usually finishes in one call. If the local port is unavailable it returns a URL to approve and you then call submit_code with the code Yandex shows. Run this once (the token lasts ~1 year); needed before the data tools if you are not signed in yet.submit_codeComplete a copy-paste sign-in started by login: pass the code Yandex showed you after you approved access.get_hostsDiscovery tool: list the sites (hosts) available to your Yandex Webmaster token, each with its host_id, URL and verification state. host_id is what every other tool needs to identify a site. Optionally pass `hostId` to also fetch that host summary (SQI, indexed/excluded page counts, site problems). Read-only. Call this first.search_queriesSearch-query analytics for a host from Yandex Search: impressions (TOTAL_SHOWS), clicks (TOTAL_CLICKS), average show/click position. Read-only. • report="top" (default): ranked list of the queries bringing the most traffic, ordered by orderBy. Use this to see which phrases people search. • report="trend": a time series. Pass queryId (from a prior "top" call) for one query's history over time, or omit it for the site's aggregate trend. Tip: cross-reference these queries/landing pages with Yandex Metrica (bounce rate, conversions) to find high-impression, low-conversion phrases worth optimizing.get_indexingHow Yandex crawls and indexes the host. Read-only. Pick a report: • report="history" (default): time series of crawled pages grouped by HTTP status class (HTTP_2XX/3XX/4XX/5XX/OTHER) — spot spikes of errors the crawler hits. • report="crawled": example crawled URLs with their HTTP code and crawl date. • report="in_search": example URLs currently present in Yandex search, with title.get_diagnosticsYandex Webmaster site diagnostics: problems detected on the host (e.g. DNS errors, slow response, robots.txt issues, 4xx alerts), each with a severity (FATAL, CRITICAL, POSSIBLE_PROBLEM, RECOMMENDATION). By default returns only ACTIVE problems (state=PRESENT), worst first. Set includeAbsent=true to also list resolved/absent problem types. Read-only.list_sitemapsList the Sitemap files Yandex knows for the host, each with its URL, type, last access date, number of URLs and error count, and where it was discovered (robots.txt, webmaster, etc.). Use it to check a sitemap is being read and is error-free. Read-only.get_external_linksInbound (external) links pointing to the host — the backlinks Yandex knows. Read-only. • report="samples" (default): example links with source page, target URL and discovery date, plus the total count available. • report="history": time series of the total external-link count over time.recrawl_statusRead-only view of the host recrawl activity. With no taskId: the remaining daily quota plus the most recent recrawl tasks and their state (IN_PROGRESS, DONE, FAILED). Pass taskId (from recrawl_submit) to check one task. Use before recrawl_submit to confirm quota is available.recrawl_submitAsk Yandex to recrawl a specific page of the host sooner. NOT read-only: each call consumes one unit of the limited daily recrawl quota (check it with recrawl_status). The URL must belong to the host and be a full absolute URL. Returns the task_id and the remaining quota. Track progress with recrawl_status using the returned task_id.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Webtools MCP
No confirmed install command for Google Webtools MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Yandex Webmaster MCP
{
"mcpServers": {
"yandex-webmaster-mcp": {
"command": "npx",
"args": [
"-y",
"@boxlab/yandex-webmaster-mcp"
],
"env": {
"YANDEX_WEBMASTER_TOKEN": "YOUR_YANDEX_WEBMASTER_TOKEN_HERE",
"YANDEX_OAUTH_CLIENT_ID": "YOUR_YANDEX_OAUTH_CLIENT_ID_HERE",
"YANDEX_OAUTH_CLIENT_SECRET": "YOUR_YANDEX_OAUTH_CLIENT_SECRET_HERE"
}
}
}
}
Frequently asked questions
Google Webtools MCP is categorized under Marketing and uses an install path we have not confirmed yet. Yandex Webmaster MCP belongs to Marketing and uses a local stdio subprocess. Pick Google Webtools MCP for marketing work and Yandex Webmaster MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Google Webtools MCP has no confirmed install command yet — follow its own setup instructions.
Google Webtools MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. Yandex Webmaster MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-webtools-mcp and yandex-webmaster-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Webtools MCP has a quality signal of 51/100 (Good) with 1 views, 0 installs and 7 GitHub stars. Yandex Webmaster MCP has 63/100 (Good) with 2 views, 0 installs and 4 GitHub stars.