tracker-mcp
traker-mcp
A Yandex Tracker MCP server with 187 tools and a skill: issues, queues, boards, sprints and automation over API v3, with a read-only mode
- 1 ★ on the repository
- Last commit
Broad access
Why this level
- The token opens the organization's work items: the agent creates, edits, moves and deletes them, and migration tools write backdated records
- Installing through `curl | bash` runs a downloaded script that sets up Node.js and client configs
Install
- Works in
- Services
Manual install
npm install -g tracker-mcp && tracker-mcp setupThe wizard asks for keys and configures the chosen client.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The token opens the organization's work items: the agent creates, edits, moves and deletes them, and migration tools write backdated records
- Installing through `curl | bash` runs a downloaded script that sets up Node.js and client configs
This is third-party code. Review the repository files before installing.
What it does
The server covers almost the whole Yandex Tracker API v3 with 187 tools. The agent searches issues with filters and the query language, creates, edits and moves them, changes statuses, handles comments, checklists and time tracking, and downloads and uploads attachments. It goes on to queues with permissions and versions, boards with sprints, projects, goals and portfolios, triggers, auto actions and workflows, and status and priority catalogs. Besides tools the server exposes the `tracker://issue/{KEY}`, `tracker://queue/{KEY}` and `tracker://board/{ID}` resources for reading context without tool calls. Ready prompts `standup`, `weekly-report`, `triage`, `sprint-review`, `close-issue` and `create-issue` appear as slash commands in clients that support prompts. A `yandex-tracker` skill ships with the server: the Tracker query language, valid field values, recipes such as "find my issues" and "close with a resolution", and API pitfalls such as a mandatory resolution on closing. All delete and bulk tools require `confirm: true`, and `TRACKER_READ_ONLY=1` leaves only the 80 read tools.
Who it is for. Project managers and teams that run work in Yandex Tracker and want to search, create and close issues from an agent chat without copying links.
Good fit when
- In the morning you need a standup digest: what closed yesterday and what is stuck in the team queue
- You want to find your open issues and close one with the resolution "Solved" without opening the interface
- A sprint is ending and the agent should prepare a board review with figures from Tracker
- Issues must be moved to another queue in bulk, with the list confirmed before running
- You want read-only access so the agent looks at Tracker but changes nothing
Not a fit when
- The team tracks work in Jira or another tracker: the server knows only the Yandex Tracker API
- You have no Yandex 360 or Yandex Cloud token and organization ID: the server will not start without them
- The agent edits and deletes too eagerly: set `TRACKER_READ_ONLY=1` if writing is not needed
- You only need a couple of issue queries: a smaller server is enough, and 187 tools load the context
Example request
Find my open issues in the TREK queue and close TASK-123 with the resolution "Solved".MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
TRACKER_TOKENrequired, secret- Yandex 360 OAuth token or Yandex Cloud IAM token.
TRACKER_ORG_IDrequired- Tracker organization ID.
TRACKER_READ_ONLY- 1 leaves only the read tools.
TRACKER_AUTH- oauth by default or iam for Yandex Cloud tokens.
Limitations
Two variables are needed: `TRACKER_TOKEN` with a Yandex 360 OAuth token or a Yandex Cloud IAM token, and `TRACKER_ORG_ID` with the organization ID. IAM tokens live up to 12 hours and require `TRACKER_AUTH=iam`. Node.js 20 or newer is required.
The `install.sh` script targets macOS, Linux and WSL; on plain Windows install manually. The script runs through `curl | bash`, so read it first rather than executing it blindly.
Some categories cover administration and backdated migration and are best left off until needed. The server does not limit token rights itself: the boundary is set by the token in Tracker.
How to disable. Remove the server from the client configuration. A globally installed package is removed with `npm uninstall -g tracker-mcp` and the skill from the agent's skills directory. The token can be revoked in Yandex 360 settings.
FAQ
How do I connect Yandex Tracker to Claude Code?
Install the server with `npm install -g tracker-mcp` and run `tracker-mcp setup`: the wizard asks for the token and organization ID, checks them against the API and configures the chosen client. Then tell the agent, for example, "find my issues".
Which tokens does the server accept?
A Yandex 360 OAuth token, starting with `y0_`, or a Yandex Cloud IAM token, starting with `t1.`. For IAM set `TRACKER_AUTH=iam`: the server then sends the `X-Cloud-Org-ID` header instead of `X-Org-ID`.
How do I make access read-only?
Set `TRACKER_READ_ONLY=1`. The server exposes only the 80 read tools and hides writing completely. In addition all `delete_*` and `bulk_*` tools require `confirm: true`.
Which clients are supported?
VS Code with Copilot, Cursor, Claude Desktop, Claude Code, opencode, Windsurf, Zed, JetBrains AI Assistant and Grok CLI. The `tracker-mcp setup` wizard lets you pick a client and writes the configuration with a backup.
Can I run the server in Docker?
Yes. The image is published to GitHub Container Registry: `docker run -i --rm -e TRACKER_TOKEN -e TRACKER_ORG_ID ghcr.io/sdamarketing/tracker-mcp`. For HTTP mode add `serve --host 0.0.0.0` and `MCP_AUTH_TOKEN`.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
Yandex Tracker MCP: 23 tools for issues and files
yandex_tracker_mcp
A compact Python Yandex Tracker server: 23 tools, attachments and a one-variable read-only mode
yandex-tracker-mcp: Tracker issues, checklists and time tracking
yandex-tracker-mcp
An independent Python MCP server for the Yandex Tracker REST API v3: issues, transitions, checklists, worklogs and time reports
Yandex Tracker MCP in Go: 180 tools with access modes
mcp-yandex-tracker
A Go server with the widest tool set for Yandex Tracker: issues, boards, sprints and worklogs, with read-only and full modes
Yandex Tracker MCP with one-click install
yandex-tracker-mcp
A Yandex Tracker MCP server with a .mcpb extension for Claude Desktop that needs no terminal: issues, comments, status transitions and a read-only mode
Yandex Tracker MCP with 146 tools
ya-tracker-mcp
Full Yandex Tracker API coverage via uvx: 146 tools for issues, projects, portfolios, goals, boards, sprints and worklogs
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| tracker-mcp (this card) | no | API key | 1 | |
| Yandex Tracker MCP Server | no | key is optional | 123 | another Tracker MCP server with a smaller tool set |
| Yandex Tracker skill on the official Python client | no | 3 | a skill with no server of its own |
README in short
The README gathers documentation tables, a description of resources and prompts, a list of tool categories, safety measures, four install methods and a client connection table. The server is published in the MCP registry as `io.github.sdamarketing/tracker-mcp`, license MIT.