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.
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.
- 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
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.
One command plus a key — uvx yandex-tracker-mcp@latest, then supply credentials