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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- In `full` mode the agent deletes issues and changes data in bulk, and destructive tools are off by default
- The OAuth token sits in `.env` next to the server and gives access to the organization issues
Install
- Works in
- Services
Manual install
./yandex-tracker-mcp install-claudeThe command registers the server in Claude Code; Codex has `install-codex`, and for other clients `snippet` prints JSON. The binary comes from the repository releases.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- In `full` mode the agent deletes issues and changes data in bulk, and destructive tools are off by default
- The OAuth token sits in `.env` next to the server and gives access to the organization issues
This is third-party code. Review the repository files before installing.
What it does
A Go MCP server opens Yandex Tracker to the agent through its API: the list holds 180 tools for issues (`issue_get`, `issue_search`, `issue_create`, `issue_transition_execute`), boards, sprints, users and worklogs. 56 of them are on by default, and the rest are enabled with glob patterns in `YANDEX_TRACKER_TOOLS`. `YANDEX_TRACKER_TOOLS_MODE` sets the access level: `read-only` keeps reading only, `read-write` (the default) adds edits without deletion, and `full` enables destructive and bulk operations. The `./yandex-tracker-mcp init` wizard asks for a token and organization, writes `.env` and registers the server in Claude Code or Codex with `install-claude` and `install-codex`. Yandex 360 and Yandex Cloud organizations are told apart by `YANDEX_TRACKER_ORG_ID` or `YANDEX_TRACKER_CLOUD_ORG_ID`.
Who it is for. Teams on Yandex Tracker that need full API coverage and tight control over which operations the agent may run.
Good fit when
- The agent has to manage issues, boards and sprints, not just read a queue
- It is safer to start in `read-only` and enable writing later
- A list of 180 tools overloads the context and a narrow set by pattern is needed
- The server has to be registered in Claude Code or Codex in a minute without editing configs by hand
Not a fit when
- You need a ready launch through `uvx` or `npx`: the server ships as a GoReleaser binary or a Docker image
- You need remote work over HTTP: the server talks to the client over stdio only
- A couple of tools for reading issues is enough: the large set is overkill
Example request
Find my open issues in the DEV queue for this week and move PROJ-42 to In ProgressMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
YANDEX_TRACKER_TOKENrequired, secret- OAuth token with access to the Yandex Tracker API
YANDEX_TRACKER_ORG_ID- Yandex 360 organization id
YANDEX_TRACKER_CLOUD_ORG_ID- Yandex Cloud organization id
YANDEX_TRACKER_TOOLS_MODE- Access mode: read-only, read-write or full
Limitations
The server talks to the client over stdio only and needs a Yandex Tracker OAuth token, and it will not start without one. Exactly one of the organization variables, `YANDEX_TRACKER_ORG_ID` or `YANDEX_TRACKER_CLOUD_ORG_ID`, must be set. Of the 180 tools, 56 are available by default, and destructive and bulk operations open only in `full` mode. The README has no installation section: the binary comes from releases or is built from the sources. The repository is young, zero stars, last commit in October 2026.
How to disable. Remove the server from the Claude Code or Codex settings, then delete the `.env` file and revoke the OAuth token in the Yandex console.
FAQ
How many tools are on from the start?
Fifty-six out of one hundred eighty: issues, boards, sprints, users and worklogs. The rest are enabled through `YANDEX_TRACKER_TOOLS`.
How do I stop the agent from deleting issues?
The default mode is enough: `full` is a deliberate choice, and only it runs deletion and bulk edits.
How do I connect it to Claude Code?
With `./yandex-tracker-mcp install-claude` if the token is already set, otherwise it offers to run the `init` wizard.
Which token is needed?
An OAuth token with access to the Yandex Tracker API, passed in `YANDEX_TRACKER_TOKEN`.
Does it work with Yandex 360 and Yandex Cloud?
Yes, the organization type is set by one of two variables: `YANDEX_TRACKER_ORG_ID` for 360 or `YANDEX_TRACKER_CLOUD_ORG_ID` for Cloud.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker MCP: 23 tools for issues and files
yandex_tracker_mcp
A compact Python Yandex Tracker server: 23 tools, attachments and a one-variable read-only mode
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
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
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
Yandex 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: 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
README in short
The README opens with a table of 180 tools with a type (read, change, destructive) and a default mark, then describes configuration through environment variables, the `YANDEX_TRACKER_TOOLS_MODE` modes and the `init` wizard with registration commands.