Yandex Tracker MCP Server
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
- 123 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Creates and modifies issues, comments and statuses in the live Tracker
- Handles organization OAuth and IAM tokens
Install
- Works in
- Services
Manual install
claude mcp add yandex-tracker uvx yandex-tracker-mcp@latest \
-e TRACKER_TOKEN=your_tracker_token_here \
-e TRACKER_CLOUD_ORG_ID=your_cloud_org_id_here \
-e TRANSPORT=stdioFor Yandex 360 replace TRACKER_CLOUD_ORG_ID with TRACKER_ORG_ID.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates and modifies issues, comments and statuses in the live Tracker
- Handles organization OAuth and IAM tokens
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent the full issue lifecycle in Yandex Tracker: create, read, update, comment, log work, attach files and move through statuses with resolutions. The agent sees queues with tags and fields, users, boards and sprints, and can search issues with Tracker query language. Projects, portfolios and goals are enabled by a flag. It supports OAuth tokens, IAM tokens and service accounts, Yandex Cloud and Yandex 360 organizations, queue access restrictions and Redis caching.
Who it is for. For project managers, product managers and developers who track work in Yandex Tracker.
Good fit when
- You need a summary of sprint or queue issues
- You want the agent to create issues after a meeting or review
- You need to close or move issues across statuses in bulk
Not a fit when
- Your issues are not in Yandex Tracker
- You cannot allow the agent to write to working queues
Example request
Show open BACKEND queue issues in the current sprint grouped by assigneeMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
TRACKER_TOKENsecret- Tracker OAuth token; one auth method is required
TRACKER_IAM_TOKENsecret- IAM token instead of OAuth
TRACKER_CLOUD_ORG_ID- Yandex Cloud organization ID
TRACKER_ORG_ID- Yandex 360 organization ID
TRACKER_ENTITIES_ENABLED- Enable projects, portfolios and goals tools
TRANSPORT- Transport: stdio or http
Limitations
Requires a Tracker token and organization ID: TRACKER_CLOUD_ORG_ID for Yandex Cloud or TRACKER_ORG_ID for Yandex 360. Projects, portfolios and goals are enabled separately. Running via uvx needs uv installed; otherwise use the Docker image.
How to disable. Run claude mcp remove yandex-tracker or delete the block from the client config; in Claude Desktop disable the extension.
FAQ
Can I limit the agent to certain queues?
Yes, the README documents queue access restrictions.
Is there a no-terminal install?
Yes, Claude Desktop has an mcpb extension in releases: download it, open it and enter the token.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
Yandex Tracker MCP without PII
Yandex Tracker MCP
A Yandex Tracker MCP server that deliberately withholds assignees and authors, returning only a whitelist of issue, comment and link fields
A Go MCP server for reading Yandex Tracker and Yandex Wiki: issues, queues, sprints, comments, pages and dynamic tables
Yandex Tracker MCP with a report scheduler
Yandex Tracker MCP
A Python Yandex Tracker MCP server with issues, a recurring report scheduler and a SQLite run history
Yandex Tracker MCP in TypeScript
yandex-tracker-mcp
A TypeScript Yandex Tracker MCP server with boards, sprints and bulk issue operations
Yandex Tracker MCP in Yandex AI Studio
Яндекс Трекер в MCP Hub
A Yandex AI Studio MCP Hub template: an agent reads Tracker issue links, creates issues, comments and goals and bulk-changes statuses and queues
Alternatives
Tools by other authors for the same tasks.
README in short
The README lists server capabilities and explains choosing the organization ID. Setup is covered for Claude Desktop via a one-file extension and manually via uvx or Docker for Claude Desktop, Claude Code, VS Code and other clients. It documents authentication options, stdio and HTTP transports, caching and security settings. A separate Russian README exists; Apache-2.0 licensed.