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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The Tracker token lets the agent create and change issues, write comments and edit workflows when the flag is on
- Issue and comment texts enter the model context and may contain someone else instruction
Install
- Works in
- Services
Manual install
claude mcp add yandex-tracker uvx --from git+https://github.com/Hollway/yandex-tracker-mcp yandex-tracker-mcp -e TRACKER_TOKEN=your_tracker_token_here -e TRACKER_CLOUD_ORG_ID=your_cloud_org_id_here -e TRANSPORT=stdioFor Yandex 360 set `TRACKER_ORG_ID` instead of `TRACKER_CLOUD_ORG_ID`; in Claude Desktop the server installs from the `.mcpb` file in the releases.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The Tracker token lets the agent create and change issues, write comments and edit workflows when the flag is on
- Issue and comment texts enter the model context and may contain someone else instruction
This is third-party code. Review the repository files before installing.
What it does
A Python MCP server connects the agent to the Yandex Tracker API: queues, issues, comments, worklogs, checklists, boards, users and search in the Tracker query language. Projects, portfolios and goals (enabled by `TRACKER_ENTITIES_ENABLED`), workflow editing (optional, `TRACKER_WORKFLOWS_WRITE_ENABLED`) and status transitions are supported. Authentication: the `TRACKER_TOKEN` OAuth token, an IAM token or service account keys; the organization is set by `TRACKER_CLOUD_ORG_ID` or `TRACKER_ORG_ID`. Transports: stdio, HTTP and the deprecated SSE. There is also a Redis cache, restriction of available queues, a Docker image and an `.mcpb` file for double-click installation in Claude Desktop.
Who it is for. Yandex Tracker administrators and team leads who connect it to Claude Desktop, Cursor or Codex and want to limit the agent to chosen queues.
Good fit when
- Claude Desktop needs Tracker without editing JSON by hand: it installs from an `.mcpb` file
- The agent should reach only a few queues, not the whole organization
- Yandex tokens expire quickly and an IAM token or service account keys with auto-refresh are needed
- Many repeated Tracker requests slow the agent and a Redis cache helps
Not a fit when
- You need a minimal server with a couple of tools: this one carries a cache, several transports and dozens of tools
- You need a single executable without Python: it launches through `uvx` or Docker
- Read-only with no write exposure at all: you must check separately which tools you left enabled
Example request
Show the comments and worklogs for PROJ-15 and find all issues in the DEV queue where I am the assigneeMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
TRACKER_TOKENrequired, secret- Yandex Tracker OAuth token (or an IAM token or service account keys)
TRACKER_CLOUD_ORG_ID- Yandex Cloud organization id
TRACKER_ORG_ID- Yandex 360 organization id
Limitations
A Yandex token (OAuth, IAM or service account keys) and exactly one organization variable are required: if you set both, every Tracker call fails. The SSE transport is marked deprecated. Writing to workflows and access to projects, portfolios and goals are off by default and are enabled by flags. Redis is needed only for the cache. The repository is active, licensed Apache-2.0, zero stars, last commit in October 2026; the documentation is also available in Russian, in `README_ru.md`.
How to disable. Remove the `.mcpb` extension from Claude Desktop or the server entry from the client configuration, stop the Docker container and revoke the token.
FAQ
How do I install it in Claude Desktop in one click?
Download the `.mcpb` file from the releases, double-click it and enter the Tracker OAuth token in the settings window.
Are both organization variables needed?
No, only one: `TRACKER_CLOUD_ORG_ID` for Yandex Cloud or `TRACKER_ORG_ID` for Yandex 360. Both at once break the calls.
Which sign-in methods exist?
An OAuth token, an IAM token or service account keys; OAuth can refresh automatically.
What is Redis for?
For an optional response cache: it speeds up repeated Tracker requests, and without it the server works as usual.
Can queues be restricted?
Yes, the settings define a list of available queues and the agent does not see the rest.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex 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
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
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
A small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
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
Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode
README in short
The README in English and Russian covers features, the organization type choice, `.mcpb` installation in Claude Desktop, manual setup through `uvx` and Docker for Claude Desktop, Claude Code, Cursor and other clients, and environment variables.