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
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Current tools only read issues, queues and users, with no data writes
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/igordeveloperr-yandex-tracker-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
Run in a terminal
claude mcp add --transport stdio --env 'YANDEX_TRACKER_TOKEN=<your YANDEX_TRACKER_TOKEN>' --env 'YANDEX_TRACKER_CLOUD_ORG_ID=<YANDEX_TRACKER_CLOUD_ORG_ID value>' --env YANDEX_TRACKER_BASE_URL=https://api.tracker.yandex.net/v2 yandex-tracker-mcp-server -- node yandex-tracker-mcp-serverOr add to the file .mcp.json, in the project
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"yandex-tracker-mcp-server","type":"stdio","command":"node","args":["yandex-tracker-mcp-server"],"env":{"YANDEX_TRACKER_TOKEN":"<your YANDEX_TRACKER_TOKEN>","YANDEX_TRACKER_CLOUD_ORG_ID":"<YANDEX_TRACKER_CLOUD_ORG_ID value>","YANDEX_TRACKER_BASE_URL":"https://api.tracker.yandex.net/v2"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"yandex-tracker-mcp-server": {
"type": "stdio",
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add yandex-tracker-mcp-server --env 'YANDEX_TRACKER_TOKEN=<your YANDEX_TRACKER_TOKEN>' --env 'YANDEX_TRACKER_CLOUD_ORG_ID=<YANDEX_TRACKER_CLOUD_ORG_ID value>' --env YANDEX_TRACKER_BASE_URL=https://api.tracker.yandex.net/v2 -- node yandex-tracker-mcp-serverOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.yandex-tracker-mcp-server]
command = "node"
args = ["yandex-tracker-mcp-server"]
env = { YANDEX_TRACKER_TOKEN = "<your YANDEX_TRACKER_TOKEN>", YANDEX_TRACKER_CLOUD_ORG_ID = "<YANDEX_TRACKER_CLOUD_ORG_ID value>", YANDEX_TRACKER_BASE_URL = "https://api.tracker.yandex.net/v2" }If the file already exists, append the block to the end.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
gemini mcp add -s user -e 'YANDEX_TRACKER_TOKEN=<your YANDEX_TRACKER_TOKEN>' -e 'YANDEX_TRACKER_CLOUD_ORG_ID=<YANDEX_TRACKER_CLOUD_ORG_ID value>' -e YANDEX_TRACKER_BASE_URL=https://api.tracker.yandex.net/v2 yandex-tracker-mcp-server node yandex-tracker-mcp-serverOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"yandex-tracker-mcp-server": {
"type": "local",
"command": [
"node",
"yandex-tracker-mcp-server"
],
"environment": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"yandex-tracker-mcp-server": {
"command": "node",
"args": [
"yandex-tracker-mcp-server"
],
"env": {
"YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>",
"YANDEX_TRACKER_CLOUD_ORG_ID": "<YANDEX_TRACKER_CLOUD_ORG_ID value>",
"YANDEX_TRACKER_BASE_URL": "https://api.tracker.yandex.net/v2"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YANDEX_TRACKER_TOKENsecret, required- OAuth токен
YANDEX_TRACKER_CLOUD_ORG_IDrequired- ID огранизации
LOG_LEVELoptional- Уровень логирования
REQUEST_TIMEOUToptional- Таймаут запроса
RATE_LIMIT_REQUESTSoptional- Лимит запросов
RATE_LIMIT_WINDOWoptional- Окно лимита запросов
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Clone Igordeveloperr/Yandex-tracker-MCP, copy .env.example to .env and set YANDEX_TRACKER_TOKEN and YANDEX_TRACKER_CLOUD_ORG_ID, run npx tsc to build, then add the node dist/index.js command as a stdio MCP server.
Other ways from the author
npx tscBuilds the TypeScript source after cloning the repo and filling in .env.
This is third-party code. Review the repository files before installing.
What it does
The server offers 14 tools for reading Yandex Tracker through the REST API v2: fetching an issue by key, current user info, a queue list, user search, issue search by filter and by Tracker's query language, and directories for issue types, priorities, statuses, issue fields, queue fields, user fields, an organization's user list, and query-language documentation. The repository's README contains a broader technical specification with issue creation, editing, comments, status transitions and prompts like sprint analysis, but at review time only the read side listed in the YandexTrackerToolName enum was implemented in the source code.
Who it is for. For people who only need to view and search Tracker issues with no risk of changing anything.
Good fit when
- You need strictly read access to Tracker issues, queues and users
- You want issue search by both filters and Tracker's query language
- You need directories of types, priorities and statuses to build queries
Not a fit when
- You need to create issues, write comments or change statuses: those tools are absent from the current code despite the README describing them
- You want a ready npm package: this only offers a from-source build
Example request
Find open, high-priority issues in the SUPPORT queue in TrackerLimitations
The repository's README is written as a technical specification and describes more capabilities (issue creation and updates, comments, status transitions, prompts) than the source code implements at review time, where only 14 read tools exist. You need a Yandex OAuth token and organization id. There is no ready npm package, only a from-source build via npx tsc and running node dist/index.js.
How to disable. Remove the server from your MCP client config and stop the node dist/index.js process.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_TRACKER_TOKEN required, secret | Yandex OAuth token for Tracker |
| YANDEX_TRACKER_CLOUD_ORG_ID required | The organization id in Yandex Tracker |
| YANDEX_TRACKER_BASE_URL | The Tracker API base URL, defaults to v2 |
Security check
- Current tools only read issues, queues and users, with no data writes
README in short
The README is written as a technical specification for a Yandex Tracker MCP server: architecture, tech stack (Node.js, TypeScript, axios, MCP SDK, zod, pino), required tools for managing issues, comments, projects and users, configuration and schema resources, prompts for sprint analysis and daily reports, and environment variables for the token and organization id. The actual code implements only the read-related part of that list.
FAQ
Can this server create issues?
No, the current code implements only read tools, even though the README describes writes as part of its technical specification.
Which Tracker API version does it use?
REST API v2, with the base URL set via the YANDEX_TRACKER_BASE_URL variable.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything