A basic Yandex Tracker MCP server
Yandex Tracker MCP Server
A simple Python MCP server for Yandex Tracker with a minimal method set: issues, comments, creation and search
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 and move issues between queues
- The Tracker token is stored in .env next to the server code
Install
Manual install
pip install -r requirements.txtInstall dependencies before setting up .env.
This is third-party code. Review the repository files before installing.
What it does
The server provides basic Yandex Tracker operations: get a project, get an issue, view comments, create an issue with queue/summary/description/type/priority/assignee fields, edit an issue, move it to another queue, count issues by query, and search them with pagination. The author explicitly calls this a basic version with a minimal method set and invites contributions for the rest.
Who it is for. For people who only need basic Tracker issue reading and creation through Claude Desktop and do not need a wide tool set.
Good fit when
- You only need basic operations: get, create, edit, move an issue
- You want small, readable Python code as a base for your own extensions
Not a fit when
- You need status transitions, checklists, time tracking or issue links
- You need a ready package without installing via mcp install
Example request
Create an issue in the TEST queue titled New task with normal priorityLimitations
No status transitions, checklists, time tracking or issue links beyond a simple two-issue link tool. The author explicitly calls this a basic version and invites contributions for the rest. Installed via the mcp install command from the MCP Python SDK rather than uvx or npx.
How to disable. Remove the Yandex Tracker server from Claude Desktop's settings.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_TRACKER_TOKEN required, secret | Yandex Tracker authorization token |
| YANDEX_TRACKER_ORG_ID required | Organization ID |
Security check
- Can create, edit and move issues between queues
- The Tracker token is stored in .env next to the server code
README in short
The Russian README explicitly calls the project a basic version with a minimal method set and invites contributions. It shows dependency installation, a .env file with the token and org ID, connecting to Claude Desktop via mcp install, and a list of nine available tools with JSON input examples.
FAQ
Can an issue's status be changed?
There is no direct status-transition tool, only get, create, edit, move to a queue and link issues are available.
How do I test the server?
The README recommends the MCP Inspector for testing functionality before connecting it to Claude Desktop.
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