SkillFoxx

Yandex Tracker MCP

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

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

Extended access

Why this level

  • Can create, edit, comment on and transition issues between statuses
  • An organization-scoped OAuth or IAM token sits in the client config
All reasons and checks
Russian stack

kawaii-snafy/yandex-tracker-mcpAuthor:kawaii-snafy

Install

Manual install

[mcp_servers.yandex-tracker]
command = "uvx"
args = ["mcp-yandex-tracker"]

[mcp_servers.yandex-tracker.env]
YANDEX_TRACKER_TOKEN = "..."
YANDEX_TRACKER_CLOUD_ORG_ID = "..."

Snippet for ~/.codex/config.toml from the README.

Access and checks

How we review

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

  • Can create, edit, comment on and transition issues between statuses
  • An organization-scoped OAuth or IAM token sits in the client config

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

What it does

The server installs via uvx as the mcp-yandex-tracker package and provides tracker_-prefixed tools for reading, searching, creating, updating, commenting on, transitioning and linking Yandex Tracker issues, plus reference lookups for queues, users, statuses, types, priorities, fields, versions and components, and a board's active sprint. It supports both cloud and non-cloud organizations through separate environment variables.

Who it is for. For developers using Codex or Claude Code who need a compact server for day-to-day Tracker issue work.

Good fit when

  • You need a ready PyPI package without building from source
  • You work in Codex or Claude Code and want one uvx-based connection method
  • You need Tracker reference data: statuses, types, priorities, components, versions

Not a fit when

  • You need checklists, worklog time tracking, or board sprints beyond the active one
  • You need Yandex Wiki access in the same server

Example request

Find open critical-priority issues in the SUPPORT queue and show their titles

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_TRACKER_TOKEN required, secret
OAuth or IAM token
YANDEX_TRACKER_CLOUD_ORG_ID
Cloud organization ID, one of two required together with YANDEX_TRACKER_ORG_ID
YANDEX_TRACKER_ORG_ID
Non-cloud organization ID
YANDEX_TRACKER_AUTH_SCHEME
OAuth by default, Bearer for IAM tokens
YANDEX_TRACKER_BASE_URL
Defaults to https://api.tracker.yandex.net
YANDEX_TRACKER_TIMEOUT
Request timeout in seconds, defaults to 30

Limitations

No checklist or worklog time-tracking tools. Board support is limited to the active sprint. Community tool, not an official Yandex package.

How to disable. Remove the server with claude mcp remove yandex-tracker, or delete the block from your Codex config.

FAQ

How do I confirm the server is connected?

With claude mcp list and claude mcp get yandex-tracker, or /mcp inside a Claude Code chat.

How does a cloud organization differ in setup?

Cloud organizations set YANDEX_TRACKER_CLOUD_ORG_ID, non-cloud ones set YANDEX_TRACKER_ORG_ID, and the auth scheme switches via YANDEX_TRACKER_AUTH_SCHEME between OAuth and Bearer for IAM tokens.

Discussion

No questions or reviews yet.

All Yandex Tracker tools
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
Russian stack

Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode

MCP serverExtended access
Russian stack

Full Yandex Tracker API coverage via uvx: 146 tools for issues, projects, portfolios, goals, boards, sprints and worklogs

MCP serverBroad access3

README in short

The English README shows connecting to Codex via ~/.codex/config.toml and to Claude Code via claude mcp add, a table of required and optional environment variables, a manual JSON-RPC check with initialize and tools/list, and links to deeper docs on integration, tools, architecture and extending the server.

README badge

Report a problem