SkillFoxx

Yandex Tracker MCP without PII

Yandex Tracker MCP

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

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Can create, edit and transition issues between statuses, and comment through the integration
  • The Yandex Cloud IAM token grants organization-level access, not just Tracker
All reasons and checks
Russian stack

damu4/yandex-tracker-mcpAuthor:damu4

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/damu4-yandex-tracker-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • Can create, edit and transition issues between statuses, and comment through the integration
  • The Yandex Cloud IAM token grants organization-level access, not just Tracker

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

What it does

The server reads, creates and updates issues, changes status, posts and edits comments, and shows an epic's issues, a project's epics, and an issue's links. Responses deliberately exclude personal data: only key, type, status, Story Points, title, description, parent/epic links, comments (id, text, dates) and links come back, no assignee or author fields. Issue creation has automatic type aliases: backend phrasing gets a BE: prefix and Backend type, frontend gets FE: and Frontend, with separate aliases for QA, bugs and autotests.

Who it is for. For teams that care about an agent never seeing or storing issue assignee and author names.

Good fit when

  • It matters to limit personal-data exposure through a field whitelist in responses
  • You need automatic issue-type prefixes (BE:, FE:) matching your team's convention
  • You need to link issues to epics and view an epic's contents

Not a fit when

  • You need assignee or author data, the server withholds it by design
  • The hardcoded BE:/FE:/QA alias scheme does not fit a different naming convention

Example request

Create a backend issue for fixing the auth bug and link it to epic VEL-1904

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_TRACKER_TOKEN required, secret
Yandex Cloud IAM token, obtained via yc iam create-token
YANDEX_TRACKER_ORG_ID required
Organization ID from Tracker's Administration section
YANDEX_TRACKER_QUEUE
Default queue

Limitations

By design it never returns assignee, author or other personal fields, this is a limitation, not a bug. The Yandex Cloud IAM token must be refreshed with yc iam create-token, a 403 Organization is not available error means the token has expired. Manual install via git clone and uv, no packaged distribution.

How to disable. Remove the yandex-tracker block from your MCP client config (~/.cursor/mcp.json, ~/.claude.json or claude_desktop_config.json).

FAQ

Why is the issue assignee missing from responses?

The server deliberately filters fields: it returns only key, type, status, Story Points, title, description, links and author-free comments, stated right at the top of the README.

What to do about a 403 Organization is not available error?

The IAM token has expired, get a new one with yc iam create-token and check that the org id matches the same organization.

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 small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups

MCP serverExtended access1
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 Russian README covers uv-based installation, obtaining and refreshing the IAM token, what not to commit to git, separate setup for Cursor, Claude Code and Claude Desktop with example configs, and eleven tools with each one's exact response shape, emphasizing the absence of personal data.

README badge

Report a problem