Yandex Tracker MCP: typed and raw v3 tools
yandex-tracker-mcp
A fastmcp-based Tracker MCP server with a hybrid interface: typed tools plus a generic v3 API call
- 0 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Typed and raw tools create and change issues, queues and other Tracker entities
- tracker_raw_request opens access to any v3 API method within the v3 domain
A similar tool with a larger community: Yandex Tracker MCP Server, 123 ★ on the repository
Install
- Works in
- Services
Manual install
uv pip install yandex-tracker-mcpInstalls the package and the tracker-mcp-stdio, tracker-mcp-http console commands.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Typed and raw tools create and change issues, queues and other Tracker entities
- tracker_raw_request opens access to any v3 API method within the v3 domain
This is third-party code. Review the repository files before installing.
What it does
The server is built on fastmcp and httpx on top of the Yandex Tracker v3 API. Typed tools follow the tracker_<domain>_<action> naming scheme, such as tracker_issue_get or tracker_queue_get_metadata, generated from an operation registry and taking parameters through path_params, query and body. A separate tracker_raw_request tool allows a direct call to any v3 method, guarded to stay within the v3 domain, for cases the typed tools do not cover. List and search tools return a unified pagination envelope with results, count, next and prev fields. It supports OAuth and Bearer tokens, X-Org-ID and X-Cloud-Org-ID headers, stdio transport and streamable HTTP.
Who it is for. For developers who want both predictable typing for common Tracker operations and an escape hatch for edge cases via a raw request.
Good fit when
- You need a stable tool naming scheme like tracker_issue_create for integrating with other systems
- You need access to a rare v3 API method not yet covered by typed tools
- You need consistent pagination across every list call
Not a fit when
- You only need Tracker API v2: the server works exclusively with v3
- You are not comfortable falling back to a raw request when a typed tool is missing
Example request
Find all open critical-priority issues in the SUPPORT queue and show their assigneesMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
YANDEX_TRACKER_TOKENrequired, secret- Tracker OAuth or Bearer token
YANDEX_TRACKER_ORG_ID- Organization ID; one of ORG_ID or CLOUD_ORG_ID is required
YANDEX_TRACKER_CLOUD_ORG_ID- Cloud organization ID as an alternative to ORG_ID
YANDEX_TRACKER_TOKEN_TYPE- OAuth by default, Bearer also supported
Limitations
Works only with Tracker API v3. Requires YANDEX_TRACKER_TOKEN and one of YANDEX_TRACKER_ORG_ID or YANDEX_TRACKER_CLOUD_ORG_ID. The operation registry is synced from Yandex's docs by a separate script and may lag behind the latest API changes.
How to disable. Remove the yandex-tracker block from your MCP client config or stop the tracker-mcp-http process.
FAQ
What if the method I need is not among the typed tools?
Call tracker_raw_request with the method, path and request body directly against the v3 API.
Does it work with a plain Bearer token instead of OAuth?
Yes, YANDEX_TRACKER_TOKEN_TYPE can be set to Bearer instead of the OAuth default.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
Yandex Tracker MCP with 146 tools
ya-tracker-mcp
Full Yandex Tracker API coverage via uvx: 146 tools for issues, projects, portfolios, goals, boards, sprints and worklogs
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
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
Yandex Tracker MCP in TypeScript
yandex-tracker-mcp
A TypeScript Yandex Tracker MCP server with boards, sprints and bulk issue operations
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Yandex Tracker MCP: typed and raw v3 tools (this card) | no | OAuth | 0 | |
| Yandex Tracker MCP in TypeScript | no | OAuth | 0 | boards, sprints |
| Yandex Tracker MCP with its own OAuth provider | no | OAuth | 0 | with its own OAuth server per user |
README in short
The README describes the project as a stable tool naming scheme with CI checks, gives install via uv pip, a table of required and optional environment variables, running the stdio and HTTP versions, a TOML MCP client config example, a description of typed and raw tools, and a link to the operation-registry sync script against Yandex's docs.