yandex-tracker-mcp: a Yandex Tracker connector for Claude
Yandex Tracker connector
A connector for claude.ai, Claude Desktop and Claude Code that works with Yandex Tracker API v3 issues, with Yandex sign-in and deletion off by default
- 0 ★ on the repository
- Last commit
Broad access
Why this level
- A Tracker token gives reading and changing issues on your behalf, and in the hosted version it is stored on the author server
- Changes and comments are visible to colleagues, and the system relies on the confirmation described in tool descriptions
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/yandex-tracker-connectorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A Tracker token gives reading and changing issues on your behalf, and in the hosted version it is stored on the author server
- Changes and comments are visible to colleagues, and the system relies on the confirmation described in tool descriptions
This is third-party code. Review the repository files before installing.
What it does
The connector searches issues in the Tracker query language, reads an entire issue with its checklist, comments, transitions, links, attachments, time and history, creates and edits issues, changes statuses with a resolution, writes Markdown comments, links issues, logs time and works with attachments. Replies are compact: users and statuses arrive as one line with an ID. Any other API method is available through `send_read_request` and `send_write_request`. Tools are named without a prefix: `search_issues`, `get_issue`, `change_status`, `log_work`, `find_users` and others. The connector runs on the author server behind a gateway at `https://agent.sergei-grigorov.com/tracker` or locally in Claude Desktop as an MCPB package. Sign-in goes through a Yandex account with an authorization code and PKCE, and the token renews itself 30 days before expiry.
Who it is for. Teams on Yandex Tracker who work in Claude and want to handle issues, statuses, comments and time tracking without switching to the web interface.
Good fit when
- You need your open issues found with a Tracker query and a total count
- An issue moves to a new status with a resolution and a comment in one command
- Time is logged as "1h 30m" and the server converts it to `PT1H30M`
- A file is attached to an issue, and text attachments are read as text
Not a fit when
- You need a fully local server without a third-party gateway: the ready connector runs on the author server
- You need boards, sprints and bulk changes as separate tools: they are available only through direct requests
- You need attachments above 20 MB or images above 5 MB: the server does not pass them
Example request
Find my open issues in the BACKEND queue, move the first to "In progress" and log 1h 30m on itMCP
- Transport
- http, stdio
- Authentication
- OAuth
Environment variables
PUBLIC_URL- Public connector address on the server
GATEWAY_SECRETsecret- Connector gateway secret, only needed on the server
Limitations
The hosted connector runs on the author server and the Tracker token is kept in its settings, so you have to trust the gateway owner. Locally the connector installs as an MCPB package in Claude Desktop and needs Node.js 22 or newer. Changes are visible to colleagues because they are made as the token owner, and deletion is off. The user list for `find_users` loads in full, up to 20,000. The repository has no license file, the last commit in September 2026, no stars.
How to disable. Remove the connector in Claude settings and revoke the token at id.yandex.ru under "Devices and services" or delete the Yandex app.
FAQ
How do I sign in?
On the server with the "Sign in with Yandex" button on the settings page, on a local install paste an OAuth token by hand. A token can be obtained at `oauth.yandex.ru/authorize`.
Can issues be deleted?
Not by default: `DELETE` through `send_write_request` is off. Changes can also be turned off entirely, leaving only read tools.
Which rights does the Yandex app need?
`tracker:read` and `tracker:write`, plus `login:info` if you want the page to show the account. The redirect URI points to `/tracker/login/callback`.
How do issue texts affect the agent?
Texts of issues, comments and attachments count as data and never as instructions, and the read tool descriptions say so.
How do I check the connection?
Call `connector_status`: it shows settings, the organization and the token owner through a `/v3/myself` request.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker MCP with one-click install
yandex-tracker-mcp
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
Yandex Tracker MCP in Python with a Redis cache and OAuth
yandex-tracker-mcp
A Python server for Yandex Tracker: one-click install into Claude Desktop, OAuth, service account keys and queue restrictions
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
tracker-mcp
traker-mcp
A Yandex Tracker MCP server with 187 tools and a skill: issues, queues, boards, sprints and automation over API v3, with a read-only mode
yandex-tracker-mcp: Tracker issues, checklists and time tracking
yandex-tracker-mcp
An independent Python MCP server for the Yandex Tracker REST API v3: issues, transitions, checklists, worklogs and time reports
Yandex Tracker MCP in Go: 180 tools with access modes
mcp-yandex-tracker
A Go server with the widest tool set for Yandex Tracker: issues, boards, sprints and worklogs, with read-only and full modes
README in short
The README covers connector capabilities, the tool list, settings, Yandex sign-in and a manual token, security measures, server deployment, limits and development.