get_global_fields
Get all global fields available in Yandex Tracker that can be used in issues
LABSCO SUMMARY
It makes you look up the workflow before it moves an issue.
The transition tools are built to keep an agent honest: issue_execute_transition only accepts an id that issue_get_transitions returned, and issue_close first reads the issue type and the queue metadata to find a valid done state — so status changes follow your actual workflow instead of guessing at ids. queue_get_fields surfacing required fields serves the same discipline on the create side.
What it is
A server for the Yandex Tracker issue tracker: 39 tools across queues, issues, workflow transitions, worklogs, comments, links and users, with full Yandex Tracker Query Language for search. Optional Redis caching and configurable queue-access restrictions.
What you get
- Queues discovered and inspected — queues_get_all, queue_get_metadata, queue_get_fields (which flags required fields via schema.required so you know what an issue must carry before creating it), queue_get_tags and queue_get_versions
- The org's shared vocabulary: get_global_fields, get_statuses, get_issue_types, get_priorities and get_resolutions, so an issue is created with values that actually exist in your instance
- Issues found and read — issues_find by queue and date, issues_count for a query total, issue_get, issue_get_comments, issue_get_links, issue_get_worklogs, issue_get_attachments, issue_get_checklist and issue_get_changelog, which pages the full history of who changed what from and to
- The full write lifecycle: issue_create, issue_update (only the fields you pass change), issue_move to another queue with a new key, and issue_get_url
- Workflow done right: issue_get_transitions lists the legal moves, issue_execute_transition takes only an id that came back from it, and issue_close finds a transition to a done status and applies a resolution
- Time tracking — issue_add_worklog, issue_update_worklog and issue_delete_worklog — and comments with issue_add_comment, issue_update_comment and issue_delete_comment, where a summonees parameter notifies people rather than an @login in the text
- Issue relationships: issue_add_link with an explicit relationship such as 'depends on', and issue_delete_link
- Users resolved — users_get_all, users_search by login, email or name, user_get and user_get_current
Requirements
A Yandex Tracker OAuth token in TRACKER_TOKEN (or an IAM token in TRACKER_IAM_TOKEN, with OAuth 2.0 dynamic auth as an alternative), plus your organization id — TRACKER_CLOUD_ORG_ID for a Yandex Cloud-managed org, or TRACKER_ORG_ID for a Yandex 360 org. Run it with uvx yandex-tracker-mcp over stdio, or from the ghcr.io/aikts/yandex-tracker-mcp image.
Setup effort
One command plus a key — uvx yandex-tracker-mcp@latest, then supply credentials
USE CASES
01
Filing an issue that passes validation
Read the queue's fields to see what is required, check the available types and priorities, then create the issue with values your instance actually accepts rather than ones the API will reject.
02
Moving a ticket through its workflow
Fetch the legal transitions for an issue, execute the one you want by its returned id, and close it with a resolution when it is done — without inventing a status the workflow does not allow.
03
Finding what needs attention
Search issues with Tracker's query language, count how many match to gauge scope, and read the ones that matter with their comments and change history.
04
Logging time and keeping people informed
Record spent time against an issue and add a comment that actually notifies the people who need to weigh in, using summonees rather than an @-mention in the body.
05
Wiring up dependencies between issues
Read an issue's existing links, add a new one with the right relationship such as 'depends on', and remove a link that no longer holds.
39 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_issue_types
Get all issue types available in Yandex Tracker that can be used when creating or updating issues
get_priorities
Get all priorities available in Yandex Tracker that can be used in issues
get_resolutions
Get all resolutions available in Yandex Tracker that can be used when closing issues
get_statuses
Get all statuses available in Yandex Tracker that can be used in issues
issue_add_comment
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_add_link
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_add_worklog
Add a worklog entry (log spent time) to a Yandex Tracker issue
issue_close
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_create
Create a new issue in a Yandex Tracker queue
issue_delete_comment
Delete a comment from a Yandex Tracker issue
issue_delete_link
Delete a link between a Yandex Tracker issue and another issue. Use issue_get_links to retrieve the link IDs for an issue.
issue_delete_worklog
Delete a worklog entry (spent time record) from a Yandex Tracker issue
issue_execute_transition
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_get
Get a Yandex Tracker issue by its id
issue_get_attachments
Get attachments of a Yandex Tracker issue by its id
issue_get_changelog
Get the change history (changelog) of a Yandex Tracker issue by its id: status transitions, field edits (who changed what from -> to and when), comment changes and executed triggers. Returns a page of entries plus 'next_cursor'. To fetch the next page, pass 'next_cursor' from the previous result as the 'cursor' argument; when 'next_cursor' is null there are no more pages.
issue_get_checklist
Get checklist items of a Yandex Tracker issue by its id
issue_get_comments
Get comments of a Yandex Tracker issue by its id
issue_get_links
Get a Yandex Tracker issue related links to other issues by its id
issue_get_transitions
Get possible status transitions for a Yandex Tracker issue. Returns list of available transitions that can be performed on the issue.
issue_get_url
Get a Yandex Tracker issue url by its id
issue_get_worklogs
Get worklogs of a Yandex Tracker issue by its id
issue_move
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_update
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_update_comment
Update an existing comment in a Yandex Tracker issue. IMPORTANT: If you need to mention/call people (notifications), use the summonees parameter.
issue_update_worklog
Update a worklog entry (spent time record) in a Yandex Tracker issue
issues_count
Get the count of Yandex Tracker issues matching a query
issues_find
Find Yandex Tracker issues by queue and/or created date
queue_create_version
Create a new version in a Yandex Tracker queue.
queue_get_fields
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_metadata
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.
queue_get_tags
Get all tags for a specific Yandex Tracker queue
queue_get_versions
Get all versions for a specific Yandex Tracker queue
queues_get_all
Find all Yandex Tracker queues available to the user (queue is a project in some sense)
user_get
Get information about a specific user by login or UID
user_get_current
Get information about the current authenticated user
users_get_all
Get information about user accounts registered in the organization
users_search
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.
BEFORE YOU INSTALL
What to know first
Tools you get
39 tools when we connected; the project documents 65. The 22 project, portfolio and goal tools register only with TRACKER_ENTITIES_ENABLED=true. The four template tools have no documented flag and may be missing from builds older than 0.8.0. TRACKER_READ_ONLY hides every write tool.
Requires
- uv installed globally (uvx on PATH)
- TRACKER_TOKEN in your environment — or TRACKER_IAM_TOKEN, or the service-account trio TRACKER_SA_KEY_ID, TRACKER_SA_SERVICE_ACCOUNT_ID, TRACKER_SA_PRIVATE_KEY
- TRACKER_CLOUD_ORG_ID (Yandex Cloud) or TRACKER_ORG_ID (Yandex 360) in your environment — exactly one; setting both makes every call fail
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx yandex-tracker-mcp@latestMCP Clients
Claude Desktop — uvx, Cursor — uvx, Windsurf — uvx, Any MCP client — uvx
JSON
{
"mcpServers": {
"yandex-tracker": {
"command": "uvx",
"args": [
"yandex-tracker-mcp@latest"
],
"env": {
"TRACKER_TOKEN": "<YOUR_TRACKER_TOKEN>",
"TRACKER_CLOUD_ORG_ID": "<YOUR_TRACKER_CLOUD_ORG_ID>"
}
}
}
}Claude Desktop — MCPB bundle
Download the *.mcpb file from GitHub Releases at https://github.com/aikts/yandex-tracker-mcp/releases/latest
Double-click the downloaded file to install it in Claude Desktop
Provide your Yandex Tracker OAuth token when prompted
Make sure the extension is enabled
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add yandex-tracker uvx yandex-tracker-mcp@latest \
-e TRACKER_TOKEN=<YOUR_TRACKER_TOKEN> \
-e TRACKER_CLOUD_ORG_ID=<YOUR_TRACKER_CLOUD_ORG_ID> \
-e TRANSPORT=stdioVS Code
Create .vscode/mcp.json in your project directory:
VS CODE · JSON
{
"inputs": [
{
"type": "promptString",
"id": "tracker-token",
"description": "Yandex Tracker Token",
"password": true
},
{
"type": "promptString",
"id": "cloud-org-id",
"description": "Yandex Cloud Organization ID"
}
],
"servers": {
"yandex-tracker": {
"type": "stdio",
"command": "uvx",
"args": [
"yandex-tracker-mcp@latest"
],
"env": {
"TRACKER_TOKEN": "${input:tracker-token}",
"TRACKER_CLOUD_ORG_ID": "${input:cloud-org-id}",
"TRANSPORT": "stdio"
}
}
}
}
