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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Write tools edit and delete comments and issues with the owner token
- Attachments are downloaded and uploaded from the computer disk, so the path should be limited to folders
Install
- Works in
- Services
Manual install
claude mcp add yandex-tracker --scope user -e TRACKER_TOKEN=<token> -e TRACKER_ORG_ID=<org_id> -- uvx --from git+https://github.com/skyfox-fur/yandex_tracker_mcp yandex-tracker-mcpFor a Yandex Cloud organization set `TRACKER_CLOUD_ORG_ID` instead of `TRACKER_ORG_ID`; `uv` must be installed.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Write tools edit and delete comments and issues with the owner token
- Attachments are downloaded and uploaded from the computer disk, so the path should be limited to folders
This is third-party code. Review the repository files before installing.
What it does
A compact Python MCP server for the Yandex Tracker API v3. Fourteen tools read data (`whoami`, `get_issue`, `search_issues`, `count_issues`, `get_comments`, `get_transitions`, `get_worklog`, `list_queues` and others) and nine write: they create and edit issues, comment, move statuses, link issues and log time. The server also downloads attachments to a local folder and attaches files to issues and comments. The token goes in `TRACKER_TOKEN`, the organization in `TRACKER_ORG_ID` (Yandex 360) or `TRACKER_CLOUD_ORG_ID` (Yandex Cloud), and an IAM token is allowed with `TRACKER_AUTH_TYPE=iam`. The `TRACKER_READ_ONLY` variable hides all write tools.
Who it is for. Developers and managers who want a small, readable bridge between Claude and Tracker with attachment handling.
Good fit when
- The agent should pull an issue attachments into a local folder and read them
- A reply on an issue should go out as a comment with an attached file
- The server installs with one `uvx` command without cloning the repository
- The agent should stay read-only, with writing disabled by a variable
Not a fit when
- You need boards, sprints, projects, portfolios and workflows: the set has none, only issues, queues and related data
- You need a remote HTTP server: the server runs locally over stdio
- The token has no write permission while the agent must change issues
Example request
Download the attachments from PROJ-7, read the logs and add a comment with conclusionsMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
TRACKER_TOKENrequired, secret- Yandex OAuth token with Tracker scopes or an IAM token
TRACKER_ORG_ID- Yandex 360 organization id
TRACKER_CLOUD_ORG_ID- Yandex Cloud organization id
TRACKER_READ_ONLY- Value 1 hides all write tools
Limitations
The server is local, over stdio, and aimed at Claude Code and Claude Desktop. An OAuth token with the `tracker:read` and `tracker:write` scopes is required (the first is enough for reading), and an IAM token lives twelve hours. File downloads and uploads are limited to folders and to 50 MB by default, and extra upload folders are allowed by `TRACKER_UPLOAD_DIRS`. Issues and queues are covered, with no boards, sprints or workflows. Zero stars, last commit in October 2026, MIT license.
How to disable. Remove the server with `claude mcp remove yandex-tracker` or the entry in `claude_desktop_config.json`, then revoke the OAuth token.
FAQ
How do I check the connection?
Open a new session and ask for a `whoami` call: the tool returns the user who owns the token.
How do I disable writing?
Set `TRACKER_READ_ONLY=1`: write tools are not registered at all, and an unrecognized value of the variable also means read-only.
Which token do I need?
A Yandex OAuth token with the `tracker:read` and `tracker:write` scopes or an IAM token with `TRACKER_AUTH_TYPE=iam`.
Where do downloaded attachments go?
To the `TRACKER_DOWNLOAD_DIR` folder in a subfolder named after the issue key, by default the user temp folder.
Is there protection against foreign instructions in issues?
The server asks the client to treat issue texts as data, but confirmation of writes stays with the client.
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: 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 Python with a Redis cache and OAuth
yandex-tracker-mcp
A Python server for Yandex Tracker: one-click install into Claude Desktop, OAuth, service account keys and queue restrictions
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
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
A small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
README in short
The README lists all 23 tools in read and write tables, the steps to get an OAuth token and organization id, connection to Claude Code and Claude Desktop, a table of environment variables and security notes.