# aikts/yandex-tracker-mcp [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/aikts/yandex-tracker-mcp  
**GitHub Stars:** 122  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aikts-yandex-tracker-mcp

## Description
MCP Server for Yandex Tracker. Provides tools for searching and retrieving information about issues, queues, users.

## Tools
Capabilities this server exposes over MCP:

- **queues_get_all** — Every queue the token may see; returns `{values, hits, pages}
- **queue_get_tags** — The tags defined in the queue
- **queue_get_versions** — The queue's versions, with dates and status
- **queue_get_components** — The queue's components as full objects, with lead, auto-assign flag and `version`; `queue_get_metadata` with `expand: ["components"]` gives ids and names only
- **queue_create_version** — Create a version in the queue
- **queue_get_fields** — The fields configured on the queue, local ones included; `schema.required` marks the mandatory ones
- **queue_get_metadata** — Name, description, default type and priority, plus whatever `expand` asks for
- **component_get** — One component with `queue`, `lead`, `assignAuto` and `version
- **component_create** — Create a component in a queue
- **component_update** — Change name, description, lead or auto-assign flag; omitted fields keep their value, `clear_lead` removes the lead
- **component_delete** — Delete a component
- **users_get_all** — A page of the organization's users; returns `{values, hits, pages}
- **user_get** — One user by login or uid
- **user_get_current** — The user the current token belongs to
- **users_search** — Find users by login, email or real name
- **get_global_fields** — Every global field of the organization, with its schema and type
- **get_statuses** — Every issue status the organization defines
- **get_issue_types** — Every issue type, for the `type` argument of `issue_create` / `issue_update
- **get_priorities** — Every priority, with `id`, `key`, `name` and `order
- **get_resolutions** — Every resolution, for the `resolution_id` of `issue_close
- **issue_templates_get_all** — The issue templates, with the `fieldTemplates` values they prefill; returns `{values, hits, pages}
- **issue_template_get** — One issue template by id
- **comment_templates_get_all** — The comment templates, with the `template` text and its `summonees` / `maillistSummonees
- **comment_template_get** — One comment template by id
- **boards_get_all** — The organization's agile boards; returns `{boards, next_cursor}
- **board_get** — One board with `autoFilterSettings` (what it collects), `estimateBy`, `useRanking` and its working `calendar
- **board_get_columns** — The board's columns with the issue statuses that land in each
- **board_get_sprints** — The board's sprints with status (`draft`, `in_progress`, `released`, `archived`) and planned/actual dates
- **issue_get** — One issue by key: the full record, the current `version` included
- **issue_get_url** — The web URL of an issue
- **issue_get_comments** — A page of comments, oldest first; returns `{comments, next_cursor}
- **issue_add_comment** — Add a comment; `summonees` is what notifies a user, an `@login` in the text notifies nobody
- **issue_update_comment** — Edit a comment
- **issue_delete_comment** — Delete a comment
- **issue_get_links** — Links to related, blocking and duplicate issues
- **issue_add_link** — Link two issues
- **issue_delete_link** — Remove a link
- **issue_get_worklogs** — The time logged on one or more issues
- **issue_add_worklog** — Log spent time
- **issue_update_worklog** — Edit a worklog entry
- **issue_delete_worklog** — Delete a worklog entry
- **issue_get_attachments** — Attachment metadata
- **issue_get_checklist** — The checklist, with the item ids the write tools need
- **issue_add_checklist_items** — Append items in order, creating the checklist if there is none
- **issue_update_checklist_item** — Change one item; the fields you omit keep their value
- **issue_delete_checklist_item** — Delete one item
- **issue_get_transitions** — The status transitions available right now, with their ids
- **issue_execute_transition** — Run a transition, returning the transitions available afterwards
- **issue_close** — Find a transition to a done status and run it with a resolution
- **issue_get_changelog** — Field edits, status transitions, comment changes and fired triggers; returns `{entries, next_cursor}
- **issue_create** — Create an issue, returning it
- **issue_update** — Change any of those fields; the ones you omit stay as they are
- **issue_move** — Move an issue to another queue, which changes its key (`TASKS-1` → `NEWQUEUE-42`)
- **issues_find** — Search issues with [Yandex Tracker Query Language](https://yandex.ru/support/tracker/ru/user/query-filter); returns `{values, hits, pages}
- **issues_count** — How many issues match a query; returns `{"count": N}

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "yandex-tracker-mcp": {
    "command": "uvx",
    "args": ["yandex-tracker-mcp@latest"],
    "env": {
      "TRACKER_TOKEN": "",
      "TRACKER_IAM_TOKEN": "",
      "TRACKER_SA_KEY_ID": "",
      "TRACKER_SA_SERVICE_ACCOUNT_ID": "",
      "TRACKER_SA_PRIVATE_KEY": "",
      "TRACKER_CLOUD_ORG_ID": "",
      "TRACKER_ORG_ID": "",
      "TRACKER_ENTITIES_ENABLED": ""
    }
  }
}
```

**Requires environment variables:** `TRACKER_TOKEN`, `TRACKER_IAM_TOKEN`, `TRACKER_SA_KEY_ID`, `TRACKER_SA_SERVICE_ACCOUNT_ID`, `TRACKER_SA_PRIVATE_KEY`, `TRACKER_CLOUD_ORG_ID`, `TRACKER_ORG_ID`, `TRACKER_ENTITIES_ENABLED` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/aikts-yandex-tracker-mcp/readme_