SkillFoxx

Type a name, a task or a service

Yandex Tracker MCP

A small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups

MCP server

Medium risk

We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.

Why this level

  • Can create, edit, comment on and transition issues between statuses
  • An organization-scoped OAuth or IAM token sits in the client config
All reasons and checks
Russian stack

kawaii-snafy/mcp-yandex-trackerAuthor:kawaii-snafy

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/kawaii-snafy-mcp-yandex-tracker

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 'YANDEX_TRACKER_TOKEN=<your YANDEX_TRACKER_TOKEN>' yandex-tracker -- uvx mcp-yandex-tracker

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

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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":"uvx","args":["mcp-yandex-tracker"],"env":{"YANDEX_TRACKER_TOKEN":"<your YANDEX_TRACKER_TOKEN>"}}'

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

{
  "servers": {
    "yandex-tracker": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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 'YANDEX_TRACKER_TOKEN=<your YANDEX_TRACKER_TOKEN>' -- uvx mcp-yandex-tracker

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

[mcp_servers.yandex-tracker]
command = "uvx"
args = ["mcp-yandex-tracker"]
env = { YANDEX_TRACKER_TOKEN = "<your YANDEX_TRACKER_TOKEN>" }

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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>' yandex-tracker uvx mcp-yandex-tracker

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

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": [
        "uvx",
        "mcp-yandex-tracker"
      ],
      "environment": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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": "uvx",
      "args": [
        "mcp-yandex-tracker"
      ],
      "env": {
        "YANDEX_TRACKER_TOKEN": "<your YANDEX_TRACKER_TOKEN>"
      }
    }
  }
}

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

Keys and settings

YANDEX_TRACKER_TOKENsecret, required
YANDEX_TRACKER_CLOUD_ORG_IDoptional

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 17dc949.

Text for your agent

Run claude mcp add --transport stdio --env YANDEX_TRACKER_TOKEN=<token> --env YANDEX_TRACKER_CLOUD_ORG_ID=<id> yandex-tracker -- uvx mcp-yandex-tracker, use YANDEX_TRACKER_ORG_ID instead of CLOUD_ORG_ID for a non-cloud organization.

Other ways from the author
[mcp_servers.yandex-tracker]
command = "uvx"
args = ["mcp-yandex-tracker"]

[mcp_servers.yandex-tracker.env]
YANDEX_TRACKER_TOKEN = "..."
YANDEX_TRACKER_CLOUD_ORG_ID = "..."

Snippet for ~/.codex/config.toml from the README.

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

What it does

The server installs via uvx as the mcp-yandex-tracker package and provides tracker_-prefixed tools for reading, searching, creating, updating, commenting on, transitioning and linking Yandex Tracker issues, plus reference lookups for queues, users, statuses, types, priorities, fields, versions and components, and a board's active sprint. It supports both cloud and non-cloud organizations through separate environment variables.

Who it is for. For developers using Codex or Claude Code who need a compact server for day-to-day Tracker issue work.

Good fit when

  • You need a ready PyPI package without building from source
  • You work in Codex or Claude Code and want one uvx-based connection method
  • You need Tracker reference data: statuses, types, priorities, components, versions

Not a fit when

  • You need checklists, worklog time tracking, or board sprints beyond the active one
  • You need Yandex Wiki access in the same server

Example request

Find open critical-priority issues in the SUPPORT queue and show their titles

Limitations

No checklist or worklog time-tracking tools. Board support is limited to the active sprint. Community tool, not an official Yandex package.

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

MCP

Transport
stdio
Authentication
API key
Environment variables
YANDEX_TRACKER_TOKEN
required, secret		OAuth or IAM token
YANDEX_TRACKER_CLOUD_ORG_ID
Cloud organization ID, one of two required together with YANDEX_TRACKER_ORG_ID
YANDEX_TRACKER_ORG_ID
Non-cloud organization ID
YANDEX_TRACKER_AUTH_SCHEME
OAuth by default, Bearer for IAM tokens
YANDEX_TRACKER_BASE_URL
Defaults to https://api.tracker.yandex.net
YANDEX_TRACKER_TIMEOUT
Request timeout in seconds, defaults to 30

Security check

  • Can create, edit, comment on and transition issues between statuses
  • An organization-scoped OAuth or IAM token sits in the client config

README in short

The English README shows connecting to Codex via ~/.codex/config.toml and to Claude Code via claude mcp add, a table of required and optional environment variables, a manual JSON-RPC check with initialize and tools/list, and links to deeper docs on integration, tools, architecture and extending the server.

FAQ

How do I confirm the server is connected?

With claude mcp list and claude mcp get yandex-tracker, or /mcp inside a Claude Code chat.

How does a cloud organization differ in setup?

Cloud organizations set YANDEX_TRACKER_CLOUD_ORG_ID, non-cloud ones set YANDEX_TRACKER_ORG_ID, and the auth scheme switches via YANDEX_TRACKER_AUTH_SCHEME between OAuth and Bearer for IAM tokens.

Editors’ pick

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

PluginMedium riskNo VPN needed292.5K
Editors’ pick

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

SkillLow risk271.4K
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
Foxx AIYandex Tracker MCP

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.