SkillFoxx

A basic Yandex Tracker MCP server

Yandex Tracker MCP Server

A simple Python MCP server for Yandex Tracker with a minimal method set: issues, comments, creation and search

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Can create, edit and move issues between queues
  • The Tracker token is stored in .env next to the server code
All reasons and checks
Russian stack

dimonb/yandex-tracker-mcpAuthor:dimonb

A similar tool with a larger community: Yandex Tracker MCP Server, 123 ★ on the repository

Install

Manual install

pip install -r requirements.txt

Install dependencies before setting up .env.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Can create, edit and move issues between queues
  • The Tracker token is stored in .env next to the server code

This is third-party code. Review the repository files before installing.

What it does

The server provides basic Yandex Tracker operations: get a project, get an issue, view comments, create an issue with queue/summary/description/type/priority/assignee fields, edit an issue, move it to another queue, count issues by query, and search them with pagination. The author explicitly calls this a basic version with a minimal method set and invites contributions for the rest.

Who it is for. For people who only need basic Tracker issue reading and creation through Claude Desktop and do not need a wide tool set.

Good fit when

  • You only need basic operations: get, create, edit, move an issue
  • You want small, readable Python code as a base for your own extensions

Not a fit when

  • You need status transitions, checklists, time tracking or issue links
  • You need a ready package without installing via mcp install

Example request

Create an issue in the TEST queue titled New task with normal priority

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_TRACKER_TOKEN required, secret
Yandex Tracker authorization token
YANDEX_TRACKER_ORG_ID required
Organization ID

Limitations

No status transitions, checklists, time tracking or issue links beyond a simple two-issue link tool. The author explicitly calls this a basic version and invites contributions for the rest. Installed via the mcp install command from the MCP Python SDK rather than uvx or npx.

How to disable. Remove the Yandex Tracker server from Claude Desktop's settings.

FAQ

Can an issue's status be changed?

There is no direct status-transition tool, only get, create, edit, move to a queue and link issues are available.

How do I test the server?

The README recommends the MCP Inspector for testing functionality before connecting it to Claude Desktop.

Discussion

No questions or reviews yet.

All Yandex Tracker tools
Russian stack

A small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups

MCP serverExtended access1
Russian stack

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

MCP serverExtended access5
Russian stack

A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language

MCP serverBroad access123
Russian stack

A Yandex Tracker MCP server that deliberately withholds assignees and authors, returning only a whitelist of issue, comment and link fields

MCP serverExtended access

README in short

The Russian README explicitly calls the project a basic version with a minimal method set and invites contributions. It shows dependency installation, a .env file with the token and org ID, connecting to Claude Desktop via mcp install, and a list of nine available tools with JSON input examples.

README badge

Report a problem