Yandex 360 (ycli) runs on your own machine — the client starts it, so there is no endpoint to ping. 802 installs a week from pypi. Last commit 10 Oct 2026.
Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations.
What the code does
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
told = subprocess.check_output(command, cwd=root, text=True, stderr=subprocess.DEVNULL)
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
told = subprocess.check_output(command, cwd=root, text=True, stderr=subprocess.DEVNULL)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Yandex 360 (ycli) and you get told the day something new turns up.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ycli -e 'YANDEX_ID_OAUTH_TOKEN=<YANDEX_ID_OAUTH_TOKEN>' -e 'YANDEX_ID_ORGANIZATION_ID=<YANDEX_ID_ORGANIZATION_ID>' -- uvx yandex-cli{
"mcpServers": {
"ycli": {
"command": "uvx",
"args": [
"yandex-cli"
],
"env": {
"YANDEX_ID_OAUTH_TOKEN": "<YANDEX_ID_OAUTH_TOKEN>",
"YANDEX_ID_ORGANIZATION_ID": "<YANDEX_ID_ORGANIZATION_ID>"
}
}
}
}[mcp_servers.ycli]
command = "uvx"
args = ["yandex-cli"]
env = { YANDEX_ID_OAUTH_TOKEN = "<YANDEX_ID_OAUTH_TOKEN>", YANDEX_ID_ORGANIZATION_ID = "<YANDEX_ID_ORGANIZATION_ID>" }{
"mcpServers": {
"ycli": {
"command": "uvx",
"args": [
"yandex-cli"
],
"env": {
"YANDEX_ID_OAUTH_TOKEN": "<YANDEX_ID_OAUTH_TOKEN>",
"YANDEX_ID_ORGANIZATION_ID": "<YANDEX_ID_ORGANIZATION_ID>"
}
}
}
}{
"servers": {
"ycli": {
"type": "stdio",
"command": "uvx",
"args": [
"yandex-cli"
],
"env": {
"YANDEX_ID_OAUTH_TOKEN": "<YANDEX_ID_OAUTH_TOKEN>",
"YANDEX_ID_ORGANIZATION_ID": "<YANDEX_ID_ORGANIZATION_ID>"
}
}
}
}Put your own values in place of
<YANDEX_ID_OAUTH_TOKEN> (Yandex OAuth token with Tracker, Wiki and Forms access), <YANDEX_ID_ORGANIZATION_ID> (Yandex 360 organization id (sent as X-Org-Id)).
The author’s registry entry marks them as required.
Alternatives to Yandex 360 (ycli)
same job, measured the same wayMCP server for Yandex 360 services (Wiki, and more) — tools for AI assistants.
Public read-only discovery tools for GST Cranes marketplace, wanted ads, and Crane Wiki.
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
Issue tracker and wiki for teams and their agents: find, file and update issues, write pages.
Read and write your team's shared, AI-readable wiki from any MCP client.
MCP server for Yandex Wiki with full-text search.
One wiki for all your agents: pages read and written over MCP, a link graph, and broken-link checks.
Read-only Wikidata tools and identity evidence. Local optional Google KG; bounded public remote.
Yandex 360 (ycli) — questions
Answers built from our own checks of this server.