Yandex Tracker MCP Server with issue validation
Yandex Tracker MCP Server
A TypeScript MCP server for Yandex Tracker with issue-validation tools against a team convention and optional Miro sync
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Writes and syncs Tracker issue data through separate write tools
- The OAuth token is passed via environment variables in the client config
Install
Manual install
npm install && npm run build && npm run startBuilds into dist/ and runs the compiled server, npm run dev is available for a quick check via tsx.
This is third-party code. Review the repository files before installing.
What it does
The server is built from TypeScript into dist/ and runs over stdio against the Yandex Tracker REST API v3. Besides regular issue read and write tools it reads rules from convention.json and checks issues against them via validate_issue and audit_queue. A sync-map.json file holds an optional mapping between Tracker issue ids and Miro boards for agent-driven sync.
Who it is for. For teams with a formalized issue-formatting convention who want an agent to check compliance against it.
Good fit when
- You need to validate issues against a team convention (validate_issue, audit_queue)
- You work in Cursor or Claude Desktop and are fine building the TypeScript project from source
- You need optional id syncing between issues and Miro boards
Not a fit when
- You have no issue-formatting convention, the convention.json rules would need to be written from scratch
- You need a ready package without an npm run build step
Example request
Audit the SUPPORT queue issues against our convention and show which ones break the rulesLimitations
Validation rules must be authored manually in convention.json, none are provided out of the box. There is no formal license, the README states "private, use as you prefer unless you add a formal license file". No npm package, source build only.
How to disable. Remove the tracker-custom block from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| TRACKER_TOKEN required, secret | Tracker OAuth token with tracker:read and tracker:write scopes |
| TRACKER_ORG_ID required | Organization ID |
| TRACKER_ORG_HEADER | X-Org-ID (Yandex 360, default) or X-Cloud-Org-ID (Yandex Cloud) |
| TRACKER_BASE_URL | Defaults to https://api.tracker.yandex.net/v3 |
| TRACKER_AUTH_SCHEME | OAuth (default) or Bearer for IAM tokens |
Security check
- Writes and syncs Tracker issue data through separate write tools
- The OAuth token is passed via environment variables in the client config
README in short
The English README covers npm-based install and build, getting a Tracker OAuth token with a curl-based check, wiring to Cursor and Claude Desktop with an absolute path to dist/index.js, and the project layout: read, write, validate and sync tools, plus convention.json and sync-map.json files.
FAQ
What does validate_issue check?
An issue against the rules described in convention.json, the team's issue-formatting convention file.
How do I get a Tracker token?
The README walks through creating an OAuth app at oauth.yandex.ru with tracker:read and tracker:write scopes and getting a token via the browser implicit flow.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything