Yandex Tracker MCP with 146 tools

ya-tracker-mcp

Full Yandex Tracker API coverage via uvx: 146 tools for issues, projects, portfolios, goals, boards, sprints and worklogs

MCP serverRussian stack

imdeniil/ya-tracker-mcpAuthor:imdeniil

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/ya-tracker-mcp

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

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'YA_TRACKER_TOKEN=<your YA_TRACKER_TOKEN>' --env 'YA_TRACKER_ORG_ID=<YA_TRACKER_ORG_ID value>' ya-tracker -- uvx ya-tracker-mcp

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

{
  "mcpServers": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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 ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_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

YA_TRACKER_TOKENsecret, required
YA_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

code --add-mcp '{"name":"ya-tracker","type":"stdio","command":"uvx","args":["ya-tracker-mcp"],"env":{"YA_TRACKER_TOKEN":"<your YA_TRACKER_TOKEN>","YA_TRACKER_ORG_ID":"<YA_TRACKER_ORG_ID value>"}}'

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

{
  "servers": {
    "ya-tracker": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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 ya-tracker --env 'YA_TRACKER_TOKEN=<your YA_TRACKER_TOKEN>' --env 'YA_TRACKER_ORG_ID=<YA_TRACKER_ORG_ID value>' -- uvx ya-tracker-mcp

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

[mcp_servers.ya-tracker]
command = "uvx"
args = ["ya-tracker-mcp"]
env = { YA_TRACKER_TOKEN = "<your YA_TRACKER_TOKEN>", YA_TRACKER_ORG_ID = "<YA_TRACKER_ORG_ID value>" }

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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

gemini mcp add -s user -e 'YA_TRACKER_TOKEN=<your YA_TRACKER_TOKEN>' -e 'YA_TRACKER_ORG_ID=<YA_TRACKER_ORG_ID value>' ya-tracker uvx ya-tracker-mcp

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_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

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_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

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "type": "local",
      "command": [
        "uvx",
        "ya-tracker-mcp"
      ],
      "environment": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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": {
    "ya-tracker": {
      "command": "uvx",
      "args": [
        "ya-tracker-mcp"
      ],
      "env": {
        "YA_TRACKER_TOKEN": "<your YA_TRACKER_TOKEN>",
        "YA_TRACKER_ORG_ID": "<YA_TRACKER_ORG_ID value>"
      }
    }
  }
}

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

Keys and settings

YA_TRACKER_TOKENsecret, required
YA_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: uv

Checked against the repository on Sep 25, 2026, commit 8da6675.

Text for your agent

Get a Yandex OAuth token with Tracker access at oauth.yandex.ru and the organization id via GET /v3/myself, then run claude mcp add ya-tracker -e YA_TRACKER_TOKEN=your-token -e YA_TRACKER_ORG_ID=your-org-id -- uvx ya-tracker-mcp.

Other ways from the author

claude mcp add ya-tracker -e YA_TRACKER_TOKEN=your-oauth-token -e YA_TRACKER_ORG_ID=your-org-id -- uvx ya-tracker-mcp

The README's command for connecting in Claude Code.

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

What it does

Built on FastMCP and the official YaTrackerApi package, the server offers 146 tools covering nearly every section of Yandex Tracker: issues (create, search, move between queues, change history), comments, status transitions, issue links, entities (projects, portfolios, goals) with key results and metrics, attachments, checklists, automations, dashboards, directories, filters, presets, imports, team settings and worklogs. Bulk operations and bulk reads are split into their own tool groups. Every tool supports a fields parameter to select only the needed response fields, saving the model's context.

Who it is for. For teams that need full Yandex Tracker API coverage, including portfolios, goals and automations, not just basic issues.

Good fit when

You need advanced Tracker entities: portfolios, goals with key results, dashboards, automations
You want a one-command uvx install with no manual build
You care about saving context by selecting specific response fields in each tool

Not a fit when

You want a compact minimal toolset: 146 tools can bloat the available function list
You have no Python environment with uv or uvx to run the package

Example request

Create a Tracker goal with key results for the launch project and link the current sprint issues to it

Limitations

You need a Yandex OAuth token with Tracker access and an organization id, found in Tracker's admin settings or via the API. The package is published on PyPI and run via uvx; no ready Docker image or .mcpb bundle is described. With so many tools, the agent may need more steps to pick the right one than with a compact server.

How to disable. Remove the server with claude mcp remove ya-tracker, or delete the ya-tracker block from your MCP client config.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
YA_TRACKER_TOKEN required, secret	Yandex OAuth token with Tracker access
YA_TRACKER_ORG_ID required	The organization id in Yandex Tracker

Security check

Can create, change and delete issues, entities, comments and attachments in the real Tracker
146 tools grant broad write access, including bulk operations

README in short

The README lists 146 tools by section: issues, comments, status transitions, links, entities (projects, portfolios, goals) with key results, attachments, checklists, automations, dashboards, directories, filters, presets, imports, team, worklogs, bulk operations and bulk reads. It shows installation for Claude Code, Claude Desktop, Cursor and Windsurf via uvx with the YA_TRACKER_TOKEN and YA_TRACKER_ORG_ID variables, and explains how to get the token and organization id. The server is built on FastMCP and the official YaTrackerApi package.

FAQ

How many tools does it have?

146, covering issues, entities like portfolios and goals, boards, sprints, automations and worklogs.

How do I find the organization id?

In Tracker's admin settings or by calling GET /v3/myself against the API.

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