mcp-yandex-tracker
A minimal Node.js MCP server for Yandex Tracker: 12 tools for issues, statuses and comments, with no external dependencies
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
- Can create, edit, comment on and transition issues between statuses
- The OAuth token sits in plain text in the client config
Install
Manual install
git clone https://github.com/slartus/mcp-yandex-tracker.git && cd mcp-yandex-tracker && npm installInstall from source, no published npm package.
This is third-party code. Review the repository files before installing.
What it does
Built on the Tracker v3 REST API, the server provides 12 tools: current user, queue list, get an issue, search with the Tracker Query Language, create and update an issue, list transitions and change status, and comments (get, add, update, delete). It runs as a single index.mjs file on the global fetch, no build step and no external npm packages beyond the test setup.
Who it is for. For developers who want a small, easy-to-read server for basic Tracker issue operations.
Good fit when
- You want a single-file server with no build step and no extra dependencies
- 12 basic operations are enough: issues, statuses, comments
- You need search with the Tracker Query Language
Not a fit when
- You need checklists, time tracking, sprints or issue links
- You need a ready npm package instead of a manual install from source
Example request
Find issues in the SUPPORT queue with status Open and show their titlesLimitations
No tools for checklists, time tracking, sprints or issue links. Installed manually via git clone and npm install, no published npm package. Requires Node.js 18+.
How to disable. Remove the yandex-tracker block from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YT_OAUTH_TOKEN required, secret | Yandex Tracker OAuth token |
| YT_ORG_ID required | Organization ID |
| YT_ORG_HEADER | X-Org-Id by default, X-Cloud-Org-Id for cloud Yandex 360 organizations |
Security check
- Can create, edit, comment on and transition issues between statuses
- The OAuth token sits in plain text in the client config
README in short
The Russian README lists the 12 tools in a table, prerequisites (Node.js 18+, OAuth token and organization X-Org-Id), installation via git clone and npm install, Claude Code configuration, and a manual smoke test through a sequence of JSON-RPC messages.
FAQ
Can an issue be moved to another status?
Yes, the transition_issue tool moves an issue through its available workflow transitions, listed by list_transitions.
How do I test the server without a client?
The README provides a ready manual smoke-test script: a sequence of initialize, tools/list and tools/call JSON-RPC messages piped into node index.mjs.
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