Yandex Tracker Mcp Server
@aikts
Enable AI assistants to securely access and manage Yandex Tracker issues, queues, users, and related data through a comprehensive MCP server. Perform advanced searches, retrieve detailed issue information, and manage queues with optional caching for improved performance. Integrat
Overview
What is Yandex Tracker Mcp Server?
A Model Context Protocol (MCP) server that provides AI assistants with secure, authenticated access to Yandex Tracker APIs—including issues, queues, comments, worklogs, and search—with optional Redis caching for performance.
How to use Yandex Tracker Mcp Server?
Set the required environment variables (TRACKER_TOKEN and either TRACKER_CLOUD_ORG_ID or TRACKER_ORG_ID). Optionally configure transports (stdio, streamable-http, or SSE), queue restrictions, and Redis caching. The server exposes MCP tools such as queues_get_all, issue_get, and issues_find.
Key features of Yandex Tracker Mcp Server
- Complete Queue Management with pagination and tag retrieval
- User account information and organizational data access
- Issue operations: details, comments, links, worklogs, attachments
- Advanced Query Language for complex filtering and sorting
- Optional Redis caching for improved response times
- Configurable queue access restrictions for security
Use cases of Yandex Tracker Mcp Server
- Retrieve and display all queues, their tags, versions, and local fields
- Fetch detailed issue information, comments, and attachments
- Search and count issues using Yandex Tracker Query Language
- Manage worklog entries and related issue links for time tracking
FAQ from Yandex Tracker Mcp Server
What environment variables are required?
A Yandex Tracker OAuth token (TRACKER_TOKEN) and one organization ID (TRACKER_CLOUD_ORG_ID or TRACKER_ORG_ID) are required.
Can I restrict which queues the server can access?
Yes, by setting TRACKER_LIMIT_QUEUES to a comma-separated list of queue keys; all tools respect this restriction.
What transport options are supported?
Stdio, streamable-http, and SSE transports are available via the TRANSPORT environment variable.
Where does cached data live?
Optional Redis caching is configured with CACHE_ENABLED, CACHE_REDIS_ENDPOINT, CACHE_REDIS_PORT, and CACHE_REDIS_DB.
Is there a limit on how many issues a search can return?
Yes, the issues_find tool returns up to 500 issues per page.
