Yandex 360 (ycli)
io.github.bim-bav0.36.0Updated Oct 2, 2026
Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations.
Overview
Lets an assistant read and write Yandex 360 Tracker issues, Wiki pages and Forms through 322 MCP tools.
- What it does
- Exposes read and write tools for Yandex 360 Tracker, Wiki and Forms, one per wrapped API operation, plus a cross-cutting status tool. Reads are annotated read-only and writes declare whether they are destructive or idempotent. Tool sets can be narrowed by service, by a curated core profile, or by individual tool names, and a read-only mode serves no write tools at all.
- When to use it
- Use it when an assistant should work with Yandex 360 content: looking up or updating Tracker issues, comments, transitions and worklogs, reading or editing Wiki pages, or inspecting Forms and their responses. A read-only start is available for cautious deployments.
- Requirements
- Runs locally over stdio, typically via uvx from the yandex-cli package with the mcp extra. Needs a Yandex OAuth token in YANDEX_ID_OAUTH_TOKEN and an organization id in YANDEX_ID_ORGANIZATION_ID, which is sent as the X-Org-Id header. The token must be issued by a registered Yandex OAuth app with Tracker, Wiki and Forms permissions.
Installation
In SourceWeft
- Open Yandex 360 (ycli) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ycli
One Yandex 360 toolkit — four ways to use it. Drive Tracker, Wiki, and Forms from a CLI, an MCP server, a Python SDK, or a Claude Code plugin. Built for AI agents first — pleasant for humans too.
[CI] [Coverage] [PyPI] [Python] [License] [Ask DeepWiki]
[ycli in action]- 🧩 One SDK, four surfaces — write logic once, use it as a CLI, an MCP server, a Python library, or a Claude Code plugin.
- 🤖 Agent-native — the MCP server exposes read and write
tracker_*,wiki_*,forms_*tools, one per SDK/CLI operation, plus a cross-cuttingstatustool (counts in Coverage), with honest annotations (reads are marked read-only; writes declare whether they are destructive/idempotent);ycli mcp start --read-onlyserves a reads-only view for cautious deployments, and--toolsets coreserves a curated everyday profile when a host limits how many tools it accepts. - 🛡️ Trustworthy — typed pydantic models, the real Yandex API quirks handled for you, and a test suite kept at 100% coverage.
- ⚡ Zero-friction start —
uv add yandex-cli,ycli auth login, go.
Install
Run it without installing, or install it as a standalone tool:
pip install yandex-cli works too. The CLI ships as both yandex-cli and the short ycli.
Using an AI harness (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, opencode, Docker)? See Install in your harness.
The SDK's ServiceAccountAuth (IAM tokens minted from a Yandex Cloud service-account key) needs
the service-account extra: uv add 'yandex-cli[service-account]'.
Quick start
Pick the surface that fits how you work.
CLI
Output formats — a global --format / -o picks how results print (the global options work before or after the subcommand: ycli -o json tracker issues get K = ycli tracker issues get K -o json; a command that declares an option of its own, like forms answers export --format, keeps it):
--jq EXPR runs a jq program over the command's JSON result and prints
like jq -r: a string comes out raw, anything else as one compact JSON value per line. It
cannot be combined with -o yaml / -o pretty, and it needs the jq Python package (a
dependency; it has no build for Windows on ARM).
Deleting asks first. A command that destroys data (every delete, clear, abort…) asks
DELETE <url> — this deletes data. Continue? on stderr when you are at a terminal, and exits 1
if you decline. In a script, a pipe or CI there is no one to ask, so it fails with exit 2 until
you pass --yes / -y: ycli tracker boards delete 7 --yes. Reads and ordinary writes never ask.
Preview a write. --dry-run sends nothing for any write: it prints the request instead
(method, URL, body; never your token), through the same -o / --jq output, and exits 0.
Reads still run, so a command that reads and then writes shows its first write only:
ycli tracker boards delete 7 --dry-run. (The two commands that ask the API itself to validate
a request, forms filling submit and wiki pages move, call that --validate-only.)
An endpoint ycli has not wrapped. ycli api PATH --service tracker|wiki|forms calls it like
gh api would, with the same auth, retries, output and exit codes:
PATH is relative to the service's base URL; a full URL of a service needs no --service, and
any other host is refused (your token never goes elsewhere). -f key=value is a string, -F is
typed (true, null, numbers, JSON, @file for a file's text, key[sub]=v to nest, key[]=v
for an array); fields of a GET or DELETE go to the query string, otherwise to a JSON body (--input FILE sends a raw body instead). -H 'Name: value' adds a header, -X sets the method, and
--dry-run, --yes and --jq behave as everywhere. --paginate follows Tracker's Link: rel="next"
and Wiki's next_cursor; Forms pages its listings in more than one way, so pass its paging
parameters with -f yourself.
MCP server (read/write)
Run it over stdio (needs the mcp extra):
Serving all 322 tools costs a large tools/list and some hosts cap a request (VS Code allows
128 tools), so pick what the session needs:
status_get is always served. The listing omits output schemas and doctest examples (results
still carry structuredContent), which cuts tools/list from about 1.9 MB to about 0.5 MB for
the full set.
For several users, serve it over HTTP: each MCP client signs its user in through Yandex ID (OAuth), and every tool call runs with that user's own Yandex token. Setup, including the Yandex OAuth app and the reverse proxy, is in Self-host over HTTP.
List the tool names a given set of flags exposes without running the server:
Point an MCP client at it — no prior install needed via uvx (tools are namespaced
tracker_*, wiki_*, forms_*):
Python SDK
Claude Code plugin
Teaches an agent to drive Yandex 360 through ycli — including the real API quirks.
See plugins/yandex-360/.
Skills (Claude Code plugin)
The skills encode the read/write commands and the gnarly Yandex API quirks
(epic-vs-parent, transition discovery, permanent wiki slugs, fields= rules, Forms
host/header traps, answers pagination).
Configure
ycli reads two values from the environment (or a .env file — cp .env.example .env):
ycli sends the org id as X-Org-Id for every service (HTTP header names are case-insensitive
per RFC 9110, so one casing serves all).
Optional settings follow the YCLI__<GROUP>__<SETTING> pattern; ycli rejects an invalid value
at startup and names the variable:
Get your credentials
Yandex issues OAuth tokens only through a registered application, so it's a one-time app registration plus one command.
1. Register an OAuth app at oauth.yandex.ru and
grant it the Tracker, Wiki, and Forms permissions (read and write — the
CLI and the MCP server both write; the read scopes alone suffice only if you run the MCP
server with ycli mcp start --read-only). Put the ClientID — and the Client secret
if you want the headless flow — in your .env (ycli reads it from there):
2. Log in. ycli auth login gets a token, detects your organization, and writes both
into .env:
- client id + secret → the device flow: ycli prints a code and a
https://ya.ru/devicelink; approve there and it captures the token — no redirect, works over SSH. - only the client id (or
--implicit) → the browser flow: ycli opens the Yandex authorize page; approve, then copy the token it displays and paste it back.
Check it any time with ycli auth status: it shows whose token it is (from Yandex ID), your
organization (its name needs the optional directory:read_organization scope; without it you
get the id and a note) and whether each service accepts the token. ycli tracker auth status
(or wiki, forms) probes just that one service. Both exit non-zero when a service rejects
the token.
Prefer to do it by hand?
Headless (device flow):
Browser (implicit): open
https://oauth.yandex.ru/authorize?response_type=token&client_id=<ClientID> in a logged-in
browser, approve, and copy the token from the page. (Plain curl can't — implicit needs an
interactive browser session.)
Organization id: tracker.yandex.ru/admin/orgs → your organization → copy the identifier.
Exit codes
A failed ycli command exits with a code that says what kind of failure it was, so a script can branch without parsing the message.
Coverage
ycli wraps 334 operations across 62 resources of the Tracker, Wiki, and Forms REST API — every one reachable from the Python SDK and the CLI, plus 322 MCP tools (321 domain-scoped + 1 cross-cutting: status) for agents.
Legend — operations ship on SDK + CLI, and the MCP server mirrors them with honest annotations: reads carry
readOnlyHint, writes carry explicit destructive/idempotent hints, andycli mcp start --read-onlyserves the reads-only view. In each table SDK and CLI mean the operation is wrapped on that surface; MCP is ✅ when the resource exposes at least one MCP tool. Resource and operation names link to the official Yandex API reference (yandex.ru/support/…/api-ref). These tables are generated from the code byscripts/gen_coverage.py— do not edit by hand.
Tracker
35 resources · 190 operations · 187 MCP tools
Issues & work items
Agile boards
Dictionaries
Fields, queues & structure
Automation & bulk
Entities, users & search
Wiki
11 resources · 58 operations · 56 MCP tools
Pages
Collaboration
Grids (dynamic tables)
Async & uploads
Identity
Forms
16 resources · 86 operations · 78 MCP tools
Surveys & questions
Responses & export
Integrations
Distribution
Media
Identity
Every resource and operation above deep-links to the Yandex API reference: 318 of 334 operations resolve to their own endpoint page and 15 to their resource's page. No public API reference exists yet for tracker.linktypes, tracker.linktypes.list, shown as plain text. See CONTRIBUTING.md for the intentional exclusions (UI-only endpoints with no public REST API) and per-method notes.
Layout
Development
See CONTRIBUTING.md for conventions and how to add an endpoint. Contributions welcome.
License
MIT © 2026 Sava Znatnov
Source: README.md at commit 834801d
Tools
0Version history
1- v0.36.0LatestOct 2, 2026
More servers like Yandex 360 (ycli)
TurboSteed MCP
io.github.vivek-turbosteed
Lets an AI assistant manage TurboSteed-hosted websites: deploy sites, handle assets, CMS content, webhooks, and contact form submissions.
pmndrs docs
io.github.pmndrs
Lets an assistant search and read the documentation and examples of pmndrs libraries such as react-three-fiber, drei, zustand and jotai.
OpenLookup
tech.thecompound
Gives an assistant eleven keyless read-only lookups for current AI model pricing, dependency health, service pricing, stack costs, and developer directories.