Yandex Tracker MCP with its own OAuth provider
yandex-tracker-mcp
A Python Tracker MCP server with a built-in OAuth Authorization Server for per-user authorization
- 0 ★ on the repository
- Last commit
Broad access
Why this level
- Without TRACKER_READ_ONLY it changes real Tracker issues on behalf of the authorized user
- Its own OAuth provider stores and encrypts user tokens on the server
- No README, which makes config review harder before production use
A similar tool with a larger community: Yandex Tracker MCP Server, 123 ★ on the repository
Install
- Works in
- Services
Manual install
pip install -e .Install from a repo clone via pyproject.toml; you then need a .env based on deploy/dev.env.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Without TRACKER_READ_ONLY it changes real Tracker issues on behalf of the authorized user
- Its own OAuth provider stores and encrypts user tokens on the server
- No README, which makes config review harder before production use
This is third-party code. Review the repository files before installing.
What it does
The Python server implements Tracker issues, queues and users, and adds its own OAuth Authorization Server on top of the MCP SDK: each user authorizes through Yandex separately, and the server exchanges the code for a token on its own side without passing the token straight to the agent, with encryption and an in-memory store. It has a separate TRACKER_READ_ONLY mode that is on by default in the dev deployment config, plus ready-made configs for three environments via separate env files and Docker Compose for deployment.
Who it is for. For teams that need a shared Tracker MCP server for several users with separate authorization for each, rather than one shared token.
Good fit when
- The server needs to serve several employees, each with their own Tracker permissions
- You need a ready read-only mode for a dev environment with no risk to live issues
- You need Streamable HTTP transport with built-in OAuth instead of manually distributing tokens
Not a fit when
- You only need a personal single-user server: a full OAuth provider is overkill
- The repo has no README, and you do not want to work out the config from source and .env examples
Example request
Show my open issues in the SUPPORT queue without changing anythingMCP
- Transport
- http
- Authentication
- OAuth
Environment variables
TRANSPORTrequired- Transport type, streamable-http in the example
OAUTH_ENABLEDrequired- Enables the built-in OAuth Authorization Server
MCP_SERVER_PUBLIC_URLrequired- The server's public address for OAuth redirects
TRACKER_READ_ONLY- true blocks write calls; on by default in the dev config
Limitations
The repository has no README: capabilities and setup were reconstructed from pyproject.toml, the CLI entry point and the deploy/*.env examples. The default OAuth store is in-memory; production needs separate configuration. TRACKER_READ_ONLY should be explicitly checked in your environment; it is on by default in the dev config.
How to disable. Stop the container with docker compose down in the deploy directory, or remove the server from your MCP client config.
FAQ
Why is there no README?
The repository has no README file; install and config were reconstructed from pyproject.toml, the CLI entry point and the deploy/*.env examples.
Can the server be limited to read-only?
Yes, TRACKER_READ_ONLY=true in dev.env blocks write calls; other environments need it set explicitly.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker MCP in Python with a Redis cache and OAuth
yandex-tracker-mcp
A Python server for Yandex Tracker: one-click install into Claude Desktop, OAuth, service account keys and queue restrictions
A Yandex Tracker MCP server: queues, issues, comments, status transitions, sprints and search in Tracker query language
Yandex Tracker MCP: 23 tools for issues and files
yandex_tracker_mcp
A compact Python Yandex Tracker server: 23 tools, attachments and a one-variable read-only mode
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 MCP in TypeScript
yandex-tracker-mcp
A TypeScript Yandex Tracker MCP server with boards, sprints and bulk issue operations
A small stdio MCP server for Yandex Tracker with tracker_* tools: issues, search, comments, transitions, links and reference lookups
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Yandex Tracker MCP with its own OAuth provider (this card) | no | OAuth | 0 | |
| Yandex Tracker MCP: typed and raw v3 tools | no | OAuth | 0 | typed and raw calls |
| Yandex Tracker MCP in TypeScript | no | OAuth | 0 | boards, sprints |
README in short
The repository has no README. It builds via pyproject.toml with the yandex-tracker-mcp = mcp_tracker.__main__:main entry point, dependencies include aiohttp, cryptography and mcp[cli], and configuration is set via three example env files for dev, stage and prod with transport, OAuth and read-only mode settings.