ycli CLI
A Yandex 360 toolkit: Tracker, Wiki and Forms via a CLI, an MCP server, a Python SDK and a Claude Code plugin
- 5 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates, edits and deletes issues, pages and forms in a live organization
- Stores an OAuth token with write scopes
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ycliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates, edits and deletes issues, pages and forms in a live organization
- Stores an OAuth token with write scopes
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.
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.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA CLI and skill for Yandex Tracker and Wiki: short output readable by people and agents alike, instead of raw MCP payloads costing thousands of tokens
A Claude Code plugin for Yandex Tracker and Wiki backed by the yandex-cli binary: 16 commands with output tuned for agent reading
A Yandex Tracker CLI built for LLM agents: issues, comments, worklogs, checklists and bulk operations, with an agent skill
A Go MCP server for reading Yandex Tracker and Yandex Wiki: issues, queues, sprints, comments, pages and dynamic tables
Yandex Tracker CLI
tracker
The tracker command-line tool for Yandex Tracker with JSON output and a ready SKILL.md workflow for agents
Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode
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.