ycli
A Yandex 360 toolkit: Tracker, Wiki and Forms via a CLI, an MCP server, a Python SDK and a Claude Code plugin
Install
uv tool install 'yandex-cli[mcp]'
ycli auth loginBefore login set YANDEX_OAUTH_CLIENT_ID of your OAuth app in .env.
This is third-party code. Review the repository files before installing.
What it does
One codebase offers four ways to work with Yandex Tracker, Wiki and Forms. The ycli CLI reads and changes issues, epics, sprints, boards, Wiki pages, forms and responses, printing a table on a terminal and JSON when piped. The MCP server mirrors the same operations for agents, labels reads and writes with different hints, and can run read-only. The Claude Code plugin adds skills that capture API quirks: epic versus parent, transition discovery, permanent Wiki slugs. The ycli auth login command obtains an OAuth token and detects the organization.
Who it is for. For developers and managers whose teams live in Yandex Tracker and Wiki and want to hand routine work to an agent or scripts.
Good fit when
- The agent needs Tracker issue context before working on code
- You need to create issues, change status or log work from the terminal
- You need to update a Wiki page or export Forms responses
Not a fit when
- You need to change workflow structure, statuses or required fields: the API does not allow it
- Your Tracker is on Yandex Cloud and you only have an IAM token without Yandex 360
Example request
What is open under epic EPIC-1 and what changed on MYQUEUE-42 this week?Limitations
Requires a Yandex OAuth token and a Yandex 360 organization ID; getting a token means registering an OAuth app with Tracker, Wiki and Forms scopes. Python 3.12 or newer. Forms hooks are not wrapped, and binary uploads and downloads are CLI and SDK only. Community project, not a Yandex product.
How to disable. Remove the plugin via /plugin, run uv tool uninstall yandex-cli and delete the yandex block from the MCP config. Revoke the token at oauth.yandex.ru.
Security check
- Creates, edits and deletes issues, pages and forms in a live organization
- Stores an OAuth token with write scopes
README in short
The README shows install from PyPI via uv, uvx or pip and a quick start for the CLI, MCP server, Python SDK and Claude Code plugin. It details getting an OAuth token: app registration, device flow and browser flow, plus manual requests. A large coverage table generated from code lists Tracker, Wiki and Forms resources with marks per interface. MIT license.
FAQ
Can I stop the agent from making changes?
Yes, ycli mcp start --read-only exposes only read tools, and the OAuth app then needs read scopes only.
How do I get a token on a headless server?
Put the OAuth app ClientID and Client secret in .env, and ycli auth login will use the device flow with a code for ya.ru/device.
Related
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI
Anthropic's official plugins for knowledge work roles: sales, support, product, marketing, legal, finance, data and enterprise search