A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with Yandex Tracker APIs. This server provides secure
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with Yandex Tracker APIs. This server provides secure, authenticated access to Yandex Tracker issues, queues, comments, worklogs, and search. That is what the yandex tracker mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Installation goes through your MCP client rather than a global install: point it at yandex-tracker-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 4 tools. What each one is for:
Parameters — - fields (optional): Fields to include in the response (e.g., ["key", "name"]). Helps optimize context window usage by selecting only needed fieldsReturns — https://tracker.yandex.ru/{issue_id}Installation — 1. Download the *.mcpb file from GitHub Releases. 2. Double-click the downloaded filePrerequisites — The following sections show how to configure the MCP server for different AI clients. You can use either uvx yandex-tracker-mcp@latest or the DockerConfiguration is passed through the environment: TRACKER_TOKEN, TRACKER_CLOUD_ORG_ID, TRACKER_ORG_ID, TRANSPORT, TRACKER_IAM_TOKEN, TRACKER_SA_KEY_ID, TRACKER_SA_SERVICE_ACCOUNT_ID, TRACKER_SA_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
uvx yandex-tracker-mcp@latest or the Docker image ghcr.io/aikts/yandex-tracker-mcp:latest. Both require these environment variables: -Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Yandex Tracker MCP's toolset — Parameters, Returns, Installation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by aikts; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Parameters | - fields (optional): Fields to include in the response (e.g., ["key", "name"]). Helps optimize context window usage by selecting only needed fields. If not specified, returns all available fields. |
| Returns | https://tracker.yandex.ru/{issue_id} |
| Installation | 1. Download the *.mcpb file from [GitHub Releases](https://github.com/aikts/yandex-tracker-mcp/releases/latest). 2. Double-click the downloaded file to install it in Claude Desktop. 3. Provide your Yandex Tracker OAuth t |
| Prerequisites | The following sections show how to configure the MCP server for different AI clients. You can use either uvx yandex-tracker-mcp@latest or the Docker image ghcr.io/aikts/yandex-tracker-mcp:latest. Both require these envir |
{
"mcpServers": {
"yandex-tracker": {
"command": "uvx",
"args": ["yandex-tracker-mcp@latest"],
"env": {
"TRACKER_TOKEN": "your_tracker_token_here",
"TRACKER_CLOUD_ORG_ID": "your_cloud_org_id_here",
"TRACKER_ORG_ID": "your_org_id_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
uvx yandex-tracker-mcp@latest or the Docker image ghcr.io/aikts/yandex-tracker-mcp:latest. Both require these environment variables: -| Variable | Description | Required |
|---|---|---|
| TRACKER_TOKEN | Credential the server authenticates with. | Yes |
| TRACKER_CLOUD_ORG_ID | Configuration value read at startup. | Optional |
| TRACKER_ORG_ID | Configuration value read at startup. | Optional |
| TRANSPORT | Configuration value read at startup. | Optional |
| TRACKER_IAM_TOKEN | Credential the server authenticates with. | Yes |
| TRACKER_SA_KEY_ID | Credential the server authenticates with. | Yes |
| TRACKER_SA_SERVICE_ACCOUNT_ID | Configuration value read at startup. | Optional |
| TRACKER_SA_PRIVATE_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.