Yandex Tracker MCP Server (copy of the aikts project)
Yandex Tracker MCP Server
A full-featured Yandex Tracker MCP server with OAuth2 and Redis caching: the same package and code as the already-cataloged aikts/yandex-tracker-mcp
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Write actions create, update and transition issues in the live Tracker
- It supports bulk operations and automation mutations (triggers, autoactions, macros)
- Start with TRACKER_READ_ONLY=true until you trust the server's behavior
Install
Manual install
{
"mcpServers": {
"yandex-tracker": {
"command": "uvx",
"args": ["yandex-tracker-mcp@latest"],
"env": {
"TRACKER_TOKEN": "your_tracker_token_here",
"TRACKER_CLOUD_ORG_ID": "your_cloud_org_id_here"
}
}
}
}Config from the README, identical to the install method of the original aikts project.
This is third-party code. Review the repository files before installing.
What it does
The repository contains the same yandex-tracker-mcp Python package at version 1.1.2, the same mcp_tracker module, and nearly the same README word for word as the aikts__yandex-tracker-mcp catalog entry: action-based tools for issues, queues, boards, sprints, components, filters, dashboards, automations and bulk operations, four authentication methods (OAuth token, IAM token, service account, dynamic OAuth 2.0 with a provider), optional Redis caching, and OAuth data stored there too with Fernet encryption. The TRACKER_READ_ONLY variable blocks all write actions.
Who it is for. Functionally identical to the original aikts/yandex-tracker-mcp; for practical use it makes more sense to install that one, which has a more active community and more stars.
Good fit when
- You already use specifically this fork for a concrete reason (for example, a pinned version in an internal project)
- You are studying the source and want to cross-check this copy separately from the original
Not a fit when
- You are starting fresh: use aikts/yandex-tracker-mcp instead, it has more stars and more active issues and releases
- You need assurance that bugs get fixed: it is unclear whether this copy stays in sync with the aikts upstream
Example request
Find open high-priority issues in the DEV queue and show their statusesLimitations
The README, badges, issue links and even the PyPI package name in this repository all point to the aikts/yandex-tracker-mcp project, which is already a separate SkillFoxx catalog entry and noticeably more active (119 stars at the time of review). It is unclear whether this is a deliberate mirror, a pre-rename draft, or a technical copy: the README does not describe any differences of its own from the original.
How to disable. Remove the yandex-tracker server from your MCP client settings.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| TRACKER_TOKEN secret | Yandex Tracker OAuth token, one of four authentication methods |
| TRACKER_CLOUD_ORG_ID | Yandex Cloud organization ID |
| TRACKER_READ_ONLY | true blocks all write actions on the server |
Security check
- Write actions create, update and transition issues in the live Tracker
- It supports bulk operations and automation mutations (triggers, autoactions, macros)
- Start with TRACKER_READ_ONLY=true until you trust the server's behavior
README in short
The README describes the full Tracker MCP server feature set: queue, issue and status management, fields, the YQL query language, Redis caching and OAuth 2.0 with dynamic tokens, and shows install via a Claude Desktop extension, uvx and Docker for Claude Desktop, Claude Code, Cursor, Windsurf, Zed and GitHub Copilot. Every repository link, issue link and the PyPI badge in the text point to the aikts project rather than to this repository.
FAQ
How does this differ from the aikts/yandex-tracker-mcp catalog entry?
As far as can be told, not at all: same code, same package, nearly the same README, but fewer signs of active maintenance.
Which entry should a new project pick?
aikts/yandex-tracker-mcp: it has more stars and more visible activity in issues and releases.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI