Yandex 360 (ycli) vs Yandex Analytics
Yandex 360 (ycli) is an MCP server published by bim-ba. Marketplaces we read that list it: 1 (Official MCP Registry). Yandex Analytics is an MCP server published by nozikov. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Yandex 360 (ycli) |  Yandex Analytics |
|---|---|---|
| Official MCP Registry | Listed Version: 0.142.0 Downloads/month (PyPI): 9 047 Downloads/week (PyPI): 1 282 Forks (GitHub): 3 Stars (GitHub): 5 Not marked · First seen |
Listed Version: 2.1.0 Downloads/month (PyPI): 114 Downloads/week (PyPI): 43 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Yandex 360 (ycli) | Yandex Analytics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 (better) | 4 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (yandex-cli) | On your machine (yandex-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 2, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bim-ba/ycli | github.com/nozikov/yandex-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Yandex 360 (ycli)
Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations.
Yandex Analytics
Read-only Yandex analytics for AI agents: Metrika, Webmaster, Direct and Wordstat.
How to run each
Yandex 360 (ycli) As a local MCP server: PyPI package
claude mcp add --env "YANDEX_ID_OAUTH_TOKEN=<YOUR_YANDEX_ID_OAUTH_TOKEN>" --env "YANDEX_ID_ORGANIZATION_ID=<YOUR_YANDEX_ID_ORGANIZATION_ID>" --transport stdio ycli -- uvx --with "yandex-cli[mcp]==0.142.0" yandex-cli mcp startRequires: YANDEX_ID_OAUTH_TOKEN (secret), YANDEX_ID_ORGANIZATION_ID
Yandex Analytics As a local MCP server: PyPI package
claude mcp add --transport stdio yandex-mcp -- uvx yandex-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Yandex 360 (ycli) asks for
YANDEX_ID_OAUTH_TOKEN (secret)YANDEX_ID_ORGANIZATION_ID
Only Yandex Analytics asks for
YANDEX_MCP_CLIENT_IDYANDEX_MCP_DEFAULT_COUNTER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Yandex 360 (ycli) · What it can do: Yandex Analytics · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.