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

MCP serverRussian stack

tentaklem1/yandex-tracker-mcpAuthor:TentakleM1

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/yandex-tracker-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio --env 'TRACKER_TOKEN=<your TRACKER_TOKEN>' --env 'TRACKER_ORG_ID=<TRACKER_ORG_ID value>' yandex-tracker -- npx -y yandex-tracker-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

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

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

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","type":"stdio","command":"npx","args":["-y","yandex-tracker-mcp"],"env":{"TRACKER_TOKEN":"<your TRACKER_TOKEN>","TRACKER_ORG_ID":"<TRACKER_ORG_ID value>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "yandex-tracker": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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 --env 'TRACKER_TOKEN=<your TRACKER_TOKEN>' --env 'TRACKER_ORG_ID=<TRACKER_ORG_ID value>' -- npx -y yandex-tracker-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yandex-tracker]
command = "npx"
args = ["-y", "yandex-tracker-mcp"]
env = { TRACKER_TOKEN = "<your TRACKER_TOKEN>", TRACKER_ORG_ID = "<TRACKER_ORG_ID value>" }

If the file already exists, append the block to the end.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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 ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

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

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

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

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "yandex-tracker-mcp"
      ],
      "environment": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

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": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-tracker-mcp"
      ],
      "env": {
        "TRACKER_TOKEN": "<your TRACKER_TOKEN>",
        "TRACKER_ORG_ID": "<TRACKER_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TRACKER_TOKENsecret, required
TRACKER_ORG_IDrequired

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 87710dd.

Text for your agent

Download yandex-tracker.mcpb from the TentakleM1/yandex-tracker-mcp releases page, drag it into Claude Desktop → Settings → Extensions, fill in the form with the OAuth token and Organization ID, or for a terminal setup run npx -y yandex-tracker-mcp with the TRACKER_TOKEN and TRACKER_ORG_ID variables.

Other ways from the author

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "npx",
      "args": ["-y", "yandex-tracker-mcp"],
      "env": { "TRACKER_TOKEN": "ваш-токен", "TRACKER_ORG_ID": "ваш-org-id" }
    }
  }
}

The same block works in claude_desktop_config.json, .claude/mcp.json, .cursor/mcp.json and .vscode/mcp.json.

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

What it does

The server offers nine Yandex Tracker tools: reading an issue by key, building its web URL without an API call, searching via Tracker's query language, listing your own open issues, creating issues with a default queue from config, adding comments from a template, listing comments, listing available status transitions, and moving status via an alias like "done" instead of the full status name. It has a read-only mode via TRACKER_READ_ONLY and a queue allowlist via TRACKER_LIMIT_QUEUES, plus field projection that requests only the needed data from the API to avoid bloating context. For non-technical users there is a .mcpb extension installed into Claude Desktop by dragging the file into settings, with no Node.js or config editing needed.

Who it is for. For teams on Yandex Tracker who want to manage issues from Claude, including non-technical users with no terminal.

Good fit when

You want a one-click install into Claude Desktop with no Node.js or terminal
You need access control: read-only mode or a limited queue list
You want short aliases for status transitions instead of exact names

Not a fit when

You need HTTP transport: it is not implemented in the current version, only stdio
You need bulk operations on issues: the tools work one issue at a time

Example request

Show my open Tracker issues and move issue ABC-123 to done

Limitations

The project is unofficial, not affiliated with or endorsed by Yandex. You need your own Yandex OAuth token and organization id; the token process differs for Yandex 360 versus a Yandex Cloud organization. Transport is stdio only, with HTTP listed as a stub. The author explicitly notes the token goes into the extension form or environment variables and must never end up in the .mcpb file.

How to disable. In Claude Desktop, remove the extension under Settings → Extensions; for a manual install, remove the yandex-tracker block from your MCP client config.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
TRACKER_TOKEN required, secret	Yandex OAuth token for Tracker
TRACKER_ORG_ID required	The organization id in Yandex Tracker
TRACKER_READ_ONLY	Blocks creating issues, comments and status changes
TRACKER_LIMIT_QUEUES	A comma-separated list of queues allowed for access

Security check

Can create issues, write comments and change statuses when read-only mode is off
The OAuth token grants access to every queue in the organization unless an allowlist is set

README in short

The Russian and English README opens with a disclaimer about its unofficial status, lists nine tools in a table marking which ones write data, and describes two install paths: a .mcpb extension for non-technical users with a settings form, and an npx command for Claude Code, Cursor, VS Code, Windsurf and Zed. It separately covers getting an OAuth token for Yandex 360 versus Yandex Cloud organizations and warns the token must never end up in the built extension file.

FAQ

Do I need Node.js to install it?

No, if you install via the .mcpb extension in Claude Desktop, it brings Node along with it.

Can I stop the agent from changing issues?

Yes, with the TRACKER_READ_ONLY variable or the Read-only mode checkbox in the extension form.

Superpowers

Editors’ pick

A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review

PluginMedium riskNo VPN needed292.5K

Skills for real engineers by Matt Pocock

Skills For Real Engineers

Editors’ pick

Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture

SkillLow risk271.4K

Spec Kit

Editors’ pick

GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation

CLIMedium riskNo VPN needed139.3K

Reference MCP servers

Model Context Protocol servers

Official

Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything

MCP serverMedium risk90.6K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Superpowers

Skills for real engineers by Matt Pocock

Spec Kit

Reference MCP servers