Yandex Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host address | 0.0.0.0 |
| PORT | No | Server port | 8000 |
| REDIS_DB | No | Redis database number | 0 |
| TRANSPORT | No | Transport mode (stdio, streamable-http, sse) | stdio |
| REDIS_PORT | No | Redis server port | 6379 |
| OAUTH_STORE | No | OAuth data storage backend (memory, redis) | memory |
| OAUTH_ENABLED | No | Enable OAuth 2.0 authentication | false |
| TRACKER_TOKEN | No | Your Yandex Tracker OAuth token | |
| REDIS_ENDPOINT | No | Redis server endpoint | localhost |
| REDIS_PASSWORD | No | Redis password (optional) | |
| TRACKER_ORG_ID | No | Your Yandex 360 organization ID | |
| OAUTH_CLIENT_ID | No | OAuth client ID (required when OAuth enabled) | |
| OAUTH_SERVER_URL | No | OAuth server URL | https://oauth.yandex.ru |
| OAUTH_TOKEN_TYPE | No | OAuth token type (Bearer, OAuth, or empty) | |
| OAUTH_USE_SCOPES | No | Whether to use OAuth scopes | true |
| TRACKER_IAM_TOKEN | No | Your IAM token for service-to-service authentication | |
| TRACKER_READ_ONLY | No | Limit OAuth to read-only permissions | false |
| TRACKER_SA_KEY_ID | No | Service account key ID for dynamic IAM token | |
| OAUTH_CLIENT_SECRET | No | OAuth client secret (required when OAuth enabled) | |
| REDIS_POOL_MAX_SIZE | No | Maximum Redis connection pool size | 10 |
| TOOLS_CACHE_ENABLED | No | Enable tools caching | false |
| TRACKER_API_BASE_URL | No | Base URL for the Yandex Tracker API | https://api.tracker.yandex.net |
| TRACKER_CLOUD_ORG_ID | No | Your Yandex Cloud organization ID | |
| TRACKER_LIMIT_QUEUES | No | Comma-separated queue keys to restrict access to specific queues | |
| MCP_SERVER_PUBLIC_URL | No | Public URL of the MCP server (required when OAuth enabled) | |
| TOOLS_CACHE_REDIS_TTL | No | Tools cache TTL in seconds | 3600 |
| TRACKER_SA_PRIVATE_KEY | No | Service account private key for dynamic IAM token | |
| TRACKER_SA_SERVICE_ACCOUNT_ID | No | Service account ID for dynamic IAM token |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queues_get_allA | Find all Yandex Tracker queues available to the user (queue is a project in some sense) |
| queue_get_tagsA | Get all tags for a specific Yandex Tracker queue |
| queue_get_versionsA | Get all versions for a specific Yandex Tracker queue |
| queue_get_fieldsA | Get fields for a specific Yandex Tracker queue. Returns list of global fields and optionally local (queue-specific) fields. The schema.required property indicates whether a field is mandatory. Use this to find available and required fields before creating an issue with issue_create tool. |
| queue_get_metadataA | Get detailed metadata about a specific Yandex Tracker queue. Returns queue information including name, description, default type/priority, and optionally expanded data like issue types with their resolutions, workflows, team members, etc. Use expand=['issueTypesConfig'] to get available resolutions for issue_close tool. |
| get_global_fieldsA | Get all global fields available in Yandex Tracker that can be used in issues |
| get_statusesA | Get all statuses available in Yandex Tracker that can be used in issues |
| get_issue_typesA | Get all issue types available in Yandex Tracker that can be used when creating or updating issues |
| get_prioritiesA | Get all priorities available in Yandex Tracker that can be used in issues |
| get_resolutionsA | Get all resolutions available in Yandex Tracker that can be used when closing issues |
| issue_get_urlA | Get a Yandex Tracker issue url by its id |
| issue_getA | Get a Yandex Tracker issue by its id |
| issue_get_commentsA | Get comments of a Yandex Tracker issue by its id |
| issue_get_linksA | Get a Yandex Tracker issue related links to other issues by its id |
| issues_findC | Find Yandex Tracker issues by queue and/or created date |
| issues_countA | Get the count of Yandex Tracker issues matching a query |
| issue_get_worklogsB | Get worklogs of a Yandex Tracker issue by its id |
| issue_get_attachmentsA | Get attachments of a Yandex Tracker issue by its id |
| issue_get_checklistA | Get checklist items of a Yandex Tracker issue by its id |
| issue_get_transitionsA | Get possible status transitions for a Yandex Tracker issue. Returns list of available transitions that can be performed on the issue. |
| users_get_allB | Get information about user accounts registered in the organization |
| users_searchA | Search user based on login, email or real name (first or last name, or both). Returns either single user or multiple users if several match the query or an empty list if no users matched. |
| user_getA | Get information about a specific user by login or UID |
| user_get_currentA | Get information about the current authenticated user |
| queue_create_versionB | Create a new version in a Yandex Tracker queue. |
| issue_execute_transitionA | Execute a status transition for a Yandex Tracker issue. IMPORTANT: You MUST first call issue_get_transitions to retrieve available transitions for the issue. Only pass a transition_id that was returned by issue_get_transitions. Do NOT use arbitrary transition IDs - the API will reject invalid transition IDs. Returns a list of new transitions available for the issue in its new status. |
| issue_closeA | Close a Yandex Tracker issue with a resolution. This is a convenience tool that automatically finds a transition to a 'done' status and executes it with the specified resolution. IMPORTANT: Before closing, you MUST: 1) Call issue_get to retrieve the issue's type field. 2) Call queue_get_metadata with expand=['issueTypesConfig'] to get available resolutions. 3) Choose a resolution from the issueTypesConfig entry matching the issue's type - each issue type has its own set of valid resolutions. Returns a list of transitions available for the issue in its new (closed) status. |
| issue_createC | Create a new issue in a Yandex Tracker queue |
| issue_updateA | Update an existing Yandex Tracker issue. Only fields that are provided will be updated; omitted fields remain unchanged. Use queue_get_fields to discover available fields before updating. |
| issue_add_worklogA | Add a worklog entry (log spent time) to a Yandex Tracker issue |
| issue_update_worklogB | Update a worklog entry (spent time record) in a Yandex Tracker issue |
| issue_delete_worklogB | Delete a worklog entry (spent time record) from a Yandex Tracker issue |
| issue_add_commentA | Add a comment to a Yandex Tracker issue. IMPORTANT: If you need to mention/call people to the discussion (so they get notifications), do NOT rely on '@login' in the text — use the |
| issue_update_commentA | Update an existing comment in a Yandex Tracker issue. IMPORTANT: If you need to mention/call people (notifications), use the |
| issue_moveA | Move a Yandex Tracker issue to a different queue. The issue will receive a new key in the target queue (e.g., TASKS-1 → NEWQUEUE-42). Returns the updated issue with its new key and queue. |
| issue_delete_commentA | Delete a comment from a Yandex Tracker issue |
| issue_add_linkA | Create a link between a Yandex Tracker issue and another issue. The |
| issue_delete_linkA | Delete a link between a Yandex Tracker issue and another issue. Use issue_get_links to retrieve the link IDs for an issue. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tracker_mcp_configuration | Retrieve configured Yandex Tracker MCP configuration. |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aikts/yandex-tracker-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server