Yandex MCP Server
A Go MCP server for reading Yandex Tracker and Yandex Wiki: issues, queues, sprints, comments, pages and dynamic tables
- 14 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads organization issues and documents with an IAM token
- Downloads attachments to the local disk
Install
- Works in
- Services
Manual install
brew install n-r-w/homebrew-tap/yandex-mcpAlternatively use go install github.com/n-r-w/yandex-mcp/cmd/yandex-mcp@latest or download a release binary.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads organization issues and documents with an IAM token
- Downloads attachments to the local disk
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent read-only access to Yandex Tracker and Yandex Wiki; the author deliberately left out write operations. In Tracker the agent searches and counts issues by filter or query, reads transitions, comments, links, changelogs, queues, boards and sprints, and downloads attachments. In Wiki it reads pages by slug or ID, attachment lists and dynamic tables. The IAM token comes from the Yandex Cloud CLI and is refreshed automatically, and a remote mode lets the MCP run on a Linux server while browser login happens on your workstation.
Who it is for. For developers and team leads who track work in Yandex Tracker and keep docs in Yandex Wiki.
Good fit when
- You want the agent to read an issue and its comments before coding
- You need a sprint or queue summary without manual searching
- You need to pull a spec or table from Yandex Wiki
Not a fit when
- The agent must create issues, change statuses or post comments
- Your organization is not in Yandex Cloud and yc is unavailable
Example request
Read issue PROJ-1423 in Tracker with all comments and find the Wiki spec page it links toMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
YANDEX_CLOUD_ORG_IDrequired- Yandex Cloud organization ID, shown by yc organization-manager organization list
YANDEX_CLI_PROFILE- yc profile used to get the IAM token, defaults to the active one
YANDEX_MCP_ATTACH_DIR- Absolute directories where attachments may be saved
Limitations
Read-only. Requires an installed, authenticated Yandex Cloud CLI (yc) and a Yandex Cloud organization ID. IAM tokens last at most 12 hours, and yc may open a browser to log in on refresh. Unofficial project. On macOS a downloaded binary must be allowed in security settings.
How to disable. Run claude mcp remove yandex or delete the yandex block from your MCP client config. Remove the binary with brew uninstall yandex-mcp or by hand.
FAQ
Why can't it edit issues?
The author kept it read-only on purpose so the language model cannot change anything in Tracker or Wiki.
How do I use two organizations?
Add two independent server entries, each with its own YANDEX_CLOUD_ORG_ID and YANDEX_CLI_PROFILE.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsA Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode
Yandex Tracker and Yandex Wiki MCP servers
MCP Framework и MCP Серверы
A monorepo of MCP servers for the Yandex Tracker API v2/v3 and Yandex Wiki on a shared framework, with an interactive connect CLI and .mcpb bundles
Yandex Tracker MCP in Yandex AI Studio
Яндекс Трекер в MCP Hub
A Yandex AI Studio MCP Hub template: an agent reads Tracker issue links, creates issues, comments and goals and bulk-changes statuses and queues
A 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
README in short
The README lists the Tracker and Wiki tools and links to detailed parameter docs. Installation covers release binaries, Homebrew, go install and building from source. Environment variables are explained: base URLs, token refresh period, allowed attachment extensions and save directories. A separate section covers remote authentication over SSH with installers for macOS, Linux and Windows. MIT licensed.