Skip to main content
Glama
aikts

Yandex Tracker MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoServer host address0.0.0.0
PORTNoServer port8000
REDIS_DBNoRedis database number0
TRANSPORTNoTransport mode (stdio, streamable-http, sse)stdio
REDIS_PORTNoRedis server port6379
OAUTH_STORENoOAuth data storage backend (memory, redis)memory
OAUTH_ENABLEDNoEnable OAuth 2.0 authenticationfalse
TRACKER_TOKENNoYour Yandex Tracker OAuth token
REDIS_ENDPOINTNoRedis server endpointlocalhost
REDIS_PASSWORDNoRedis password (optional)
TRACKER_ORG_IDNoYour Yandex 360 organization ID
OAUTH_CLIENT_IDNoOAuth client ID (required when OAuth enabled)
OAUTH_SERVER_URLNoOAuth server URLhttps://oauth.yandex.ru
OAUTH_TOKEN_TYPENoOAuth token type (Bearer, OAuth, or empty)
OAUTH_USE_SCOPESNoWhether to use OAuth scopestrue
TRACKER_IAM_TOKENNoYour IAM token for service-to-service authentication
TRACKER_READ_ONLYNoLimit OAuth to read-only permissionsfalse
TRACKER_SA_KEY_IDNoService account key ID for dynamic IAM token
OAUTH_CLIENT_SECRETNoOAuth client secret (required when OAuth enabled)
REDIS_POOL_MAX_SIZENoMaximum Redis connection pool size10
TOOLS_CACHE_ENABLEDNoEnable tools cachingfalse
TRACKER_API_BASE_URLNoBase URL for the Yandex Tracker APIhttps://api.tracker.yandex.net
TRACKER_CLOUD_ORG_IDNoYour Yandex Cloud organization ID
TRACKER_LIMIT_QUEUESNoComma-separated queue keys to restrict access to specific queues
MCP_SERVER_PUBLIC_URLNoPublic URL of the MCP server (required when OAuth enabled)
TOOLS_CACHE_REDIS_TTLNoTools cache TTL in seconds3600
TRACKER_SA_PRIVATE_KEYNoService account private key for dynamic IAM token
TRACKER_SA_SERVICE_ACCOUNT_IDNoService account ID for dynamic IAM token

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 summonees parameter instead.

issue_update_commentA

Update an existing comment in a Yandex Tracker issue. IMPORTANT: If you need to mention/call people (notifications), use the summonees parameter.

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 relationship describes how the current issue (issue_id) relates to the linked issue. For example, 'depends on' means issue_id depends on the linked issue, while 'is dependent by' means the linked issue depends on issue_id. Use 'relates' for a simple connection. Returns the created link.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
tracker_mcp_configurationRetrieve 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