SkillFoxx

Yandex Tracker MCP Server with issue validation

Yandex Tracker MCP Server

A TypeScript MCP server for Yandex Tracker with issue-validation tools against a team convention and optional Miro sync

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Writes and syncs Tracker issue data through separate write tools
  • The OAuth token is passed via environment variables in the client config
All reasons and checks
Russian stack

dchuhin/tracker-mcp-serverAuthor:DChuhin

Install

Manual install

npm install && npm run build && npm run start

Builds into dist/ and runs the compiled server, npm run dev is available for a quick check via tsx.

Access and checks

How we review

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

  • Writes and syncs Tracker issue data through separate write tools
  • The OAuth token is passed via environment variables in the client config

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

What it does

The server is built from TypeScript into dist/ and runs over stdio against the Yandex Tracker REST API v3. Besides regular issue read and write tools it reads rules from convention.json and checks issues against them via validate_issue and audit_queue. A sync-map.json file holds an optional mapping between Tracker issue ids and Miro boards for agent-driven sync.

Who it is for. For teams with a formalized issue-formatting convention who want an agent to check compliance against it.

Good fit when

  • You need to validate issues against a team convention (validate_issue, audit_queue)
  • You work in Cursor or Claude Desktop and are fine building the TypeScript project from source
  • You need optional id syncing between issues and Miro boards

Not a fit when

  • You have no issue-formatting convention, the convention.json rules would need to be written from scratch
  • You need a ready package without an npm run build step

Example request

Audit the SUPPORT queue issues against our convention and show which ones break the rules

MCP

Transport
stdio
Authentication
API key

Environment variables

TRACKER_TOKEN required, secret
Tracker OAuth token with tracker:read and tracker:write scopes
TRACKER_ORG_ID required
Organization ID
TRACKER_ORG_HEADER
X-Org-ID (Yandex 360, default) or X-Cloud-Org-ID (Yandex Cloud)
TRACKER_BASE_URL
Defaults to https://api.tracker.yandex.net/v3
TRACKER_AUTH_SCHEME
OAuth (default) or Bearer for IAM tokens

Limitations

Validation rules must be authored manually in convention.json, none are provided out of the box. There is no formal license, the README states "private, use as you prefer unless you add a formal license file". No npm package, source build only.

How to disable. Remove the tracker-custom block from your MCP client config.

FAQ

What does validate_issue check?

An issue against the rules described in convention.json, the team's issue-formatting convention file.

How do I get a Tracker token?

The README walks through creating an OAuth app at oauth.yandex.ru with tracker:read and tracker:write scopes and getting a token via the browser implicit flow.

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 TypeScript Yandex Tracker MCP server with boards, sprints and bulk issue operations

MCP serverBroad access
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

A TypeScript MCP server for reading Yandex Tracker: issues, filter and query-language search, queues, users, and type and status directories

MCP serverExtended access3
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

README in short

The English README covers npm-based install and build, getting a Tracker OAuth token with a curl-based check, wiring to Cursor and Claude Desktop with an absolute path to dist/index.js, and the project layout: read, write, validate and sync tools, plus convention.json and sync-map.json files.

README badge

Report a problem