Log inSubmit server
Yandex Tracker MCP logo

Yandex Tracker MCP

by aikts

Connects AI assistants to Yandex Tracker for browsing queues, users, metadata, boards, sprints, and issues.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Yandex Tracker MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aikts-yandex-tracker-mcp": {
      "command": "uvx",
      "args": [
        "yandex-tracker-mcp@latest"
      ],
      "env": {
        "TRACKER_TOKEN": "YOUR_VALUE_HERE",
        "TRACKER_IAM_TOKEN": "YOUR_VALUE_HERE",
        "TRACKER_SA_KEY_ID": "YOUR_VALUE_HERE",
        "TRACKER_SA_SERVICE_ACCOUNT_ID": "YOUR_VALUE_HERE",
        "TRACKER_SA_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "TRACKER_CLOUD_ORG_ID": "YOUR_VALUE_HERE",
        "TRACKER_ORG_ID": "YOUR_VALUE_HERE",
        "TRACKER_ENTITIES_ENABLED": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx yandex-tracker-mcp@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

aikts/yandex-tracker-mcp MCP server exposes authenticated Yandex Tracker data and selected queue and component management actions through MCP tools. It can retrieve issues, queues, users, fields, statuses, templates, boards, sprints, and issue URLs, while also creating or updating queue components and versions. Run it with uvx or Docker using a Tracker authentication method and exactly one organization ID. Reach for it when an MCP client needs structured access to Yandex Tracker rather than browser-based interaction.

Use cases

  • Find an issue by its Yandex Tracker key
  • Inspect queue fields and required attributes
  • Search organization users by email or name
  • Review board columns and sprint dates
  • Create or update queue components

Key features

  • Issue, queue, user, and metadata retrieval
  • Queue version and component management
  • Board, column, and sprint inspection
  • User search and current-user lookup
  • Optional Redis caching
  • Stdio, SSE, and HTTP transport options

Tools55

What Yandex Tracker MCP lets your agent do. Expand a tool for its parameters.

Self-reported~989 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

23/23 checks healthy over the last 84d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · yandex-tracker-mcp@latest (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars122Stargazers on the source repository.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed55Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Yandex Tracker MCP works

What aikts/yandex-tracker-mcp MCP server does

The aikts/yandex-tracker-mcp MCP server connects MCP-compatible AI clients to the Yandex Tracker API. It is intended for assistants that need to inspect Tracker configuration and records, identify users, look up issue metadata, or retrieve agile planning information.

Issue access includes retrieving a complete issue by key, including its current version, and obtaining the issue's web URL. Queue tools can list visible queues and inspect their tags, versions, components, fields, and metadata. The server also exposes actions for creating versions and creating, changing, or deleting queue components.

User tools support organization-wide listing with pagination, lookup by login or UID, search by login, email, or real name, and retrieval of the user associated with the current token. Additional read tools cover global fields, statuses, issue types, priorities, resolutions, issue templates, comment templates, boards, board columns, and sprints.

How it works

The aikts/yandex-tracker-mcp MCP server runs as a local MCP process and calls Yandex Tracker with configured credentials. MCP clients communicate with the process over stdio in the supplied examples; the project also documents stdio, SSE, and HTTP transport options.

Several list endpoints return pagination data. Queue and user listings provide values, hits, and pages, while board listings use a next_cursor. Board and sprint tools expose planning details such as board columns, sprint status, and planned or actual dates. Queue component responses can include lead, automatic assignment, and version information.

Optional Redis caching is documented for performance, and queue access restrictions are available as configurable security controls.

Setup and configuration

To run the aikts/yandex-tracker-mcp MCP server, install uv for the package-based method or use Docker. Supply one authentication option: TRACKER_TOKEN, TRACKER_IAM_TOKEN, or the three service-account variables. Also set exactly one organization variable: TRACKER_CLOUD_ORG_ID for a Yandex Cloud organization or TRACKER_ORG_ID for a Yandex 360 organization. Setting both organization variables causes Tracker calls to fail.

Claude Desktop, Claude Code, Cursor, Windsurf, and Zed configuration examples are included in the README. Claude Desktop can also install a release .mcpb extension and request an OAuth token during setup. Zed requires a Preview version with MCP support. The examples use either uvx or the image ghcr.io/aikts/yandex-tracker-mcp:latest.

Tools and capabilities

  • Browse queues, queue metadata, tags, versions, fields, and components.
  • Create queue versions and manage queue components, including clearing a component lead.
  • List, search, and inspect organization users, including the current token owner.
  • Retrieve issue types, statuses, priorities, resolutions, fields, and templates.
  • Inspect agile boards, columns, sprints, issue records, and issue URLs.
  • Use queue and user list results with their exposed pagination fields.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Yandex Tracker MCP

aikts/yandex-tracker-mcp is an MCP server that connects AI assistants to the Yandex Tracker API. Its main tools retrieve issues, queues, users, fields, statuses, templates, boards, sprints, and issue URLs, and manage queue versions and components. It authenticates with Tracker credentials and an organization ID.

Install it with uvx or run the published Docker image. Configure the MCP client to launch `uvx yandex-tracker-mcp@latest` or `ghcr.io/aikts/yandex-tracker-mcp:latest`, then provide an authentication variable and exactly one organization ID. Claude Desktop also supports installing the release `.mcpb` extension.

Set one authentication method and one organization ID. Authentication can use `TRACKER_TOKEN`, `TRACKER_IAM_TOKEN`, or the service-account variables. Choose either `TRACKER_CLOUD_ORG_ID` or `TRACKER_ORG_ID`; setting both makes Tracker calls fail.

Yes, Cursor is documented as a supported client. Add the server to `.cursor/mcp.json` for a project or `~/.cursor/mcp.json` globally, launch it with uvx or Docker, and provide the required Tracker authentication and organization variables.

Yes, it can retrieve, create, update, and delete queue components. Updates can change a component's name, description, lead, or automatic-assignment flag; the `clear_lead` option removes an existing lead.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewYandex Tracker MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aikts-yandex-tracker-mcp?style=directory)](https://allmcps.com/mcp/aikts-yandex-tracker-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/aikts-yandex-tracker-mcp"><img src="https://allmcps.com/api/badge/aikts-yandex-tracker-mcp?style=directory" alt="Yandex Tracker MCP on AllMCPs" /></a>