mcp-yandex-tracker
A minimal Node.js MCP server for Yandex Tracker: 12 tools for issues, statuses and comments, with no external dependencies
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Can create, edit, comment on and transition issues between statuses
- The OAuth token sits in plain text in the client config
A similar tool with a larger community: Yandex Tracker MCP Server, 123 ★ on the repository
Install
- Works in
- Services
Manual install
git clone https://github.com/slartus/mcp-yandex-tracker.git && cd mcp-yandex-tracker && npm installInstall from source, no published npm package.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Can create, edit, comment on and transition issues between statuses
- The OAuth token sits in plain text in the client config
This is third-party code. Review the repository files before installing.
What it does
Built on the Tracker v3 REST API, the server provides 12 tools: current user, queue list, get an issue, search with the Tracker Query Language, create and update an issue, list transitions and change status, and comments (get, add, update, delete). It runs as a single index.mjs file on the global fetch, no build step and no external npm packages beyond the test setup.
Who it is for. For developers who want a small, easy-to-read server for basic Tracker issue operations.
Good fit when
- You want a single-file server with no build step and no extra dependencies
- 12 basic operations are enough: issues, statuses, comments
- You need search with the Tracker Query Language
Not a fit when
- You need checklists, time tracking, sprints or issue links
- You need a ready npm package instead of a manual install from source
Example request
Find issues in the SUPPORT queue with status Open and show their titlesMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YT_OAUTH_TOKENrequired, secret- Yandex Tracker OAuth token
YT_ORG_IDrequired- Organization ID
YT_ORG_HEADER- X-Org-Id by default, X-Cloud-Org-Id for cloud Yandex 360 organizations
Limitations
No tools for checklists, time tracking, sprints or issue links. Installed manually via git clone and npm install, no published npm package. Requires Node.js 18+.
How to disable. Remove the yandex-tracker block from your MCP client config.
FAQ
Can an issue be moved to another status?
Yes, the transition_issue tool moves an issue through its available workflow transitions, listed by list_transitions.
How do I test the server without a client?
The README provides a ready manual smoke-test script: a sequence of initialize, tools/list and tools/call JSON-RPC messages piped into node index.mjs.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
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
Read-only Yandex Tracker MCP server in TypeScript
yandex-tracker-mcp-server
A TypeScript MCP server for reading Yandex Tracker: issues, filter and query-language search, queues, users, and type and status directories
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
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
Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode
README in short
The Russian README lists the 12 tools in a table, prerequisites (Node.js 18+, OAuth token and organization X-Org-Id), installation via git clone and npm install, Claude Code configuration, and a manual smoke test through a sequence of JSON-RPC messages.