Find all Yandex Tracker queues available to the user (a queue is a project in some sense). page defaults to None and fetches ALL pages; pass a page number only when the result does not fit the context window.

Get all tags for a specific Yandex Tracker queue

Get all versions for a specific Yandex Tracker queue

Get the components (in russian - 'компоненты') of a Yandex Tracker queue with lead, auto-assign flag and version. queue_get_metadata with expand=['components'] names them only (id and name); the id is what issue_create / issue_update take in components.

Get the fields configured on a Yandex Tracker queue (in russian - 'поля очереди'), its local ones included; schema.required marks the mandatory ones. Not the whole registry: system fields such as parent or estimation are settable without appearing here, and get_global_fields lists every organization field.

Get detailed metadata about a specific Yandex Tracker queue: name, description, default type and priority, plus the sections named in expand (issue types with their resolutions, workflows, team, ...). Use expand=['issueTypesConfig'] for the resolutions issue_close needs.

Get all global fields available in Yandex Tracker that can be used in issues

Get all statuses available in Yandex Tracker that can be used in issues

Get all issue types available in Yandex Tracker that can be used when creating or updating issues

Get the issue priority levels of Yandex Tracker - trivial, minor, normal, critical, blocker and whatever else the organization configured - with the id and key that issue_create and issue_update accept in priority. The list is organization-wide: a queue may still reject a priority it does not use.

Get all resolutions available in Yandex Tracker that can be used when closing issues

Get a Yandex Tracker issue url by its id

Get the issue templates (in russian - 'шаблоны задач') configured in Yandex Tracker, optionally scoped to a queue - read one before issue_create instead of inventing a structure. The issue body is in fieldTemplates.description; the template's own description describes the template.

Get a single Yandex Tracker issue template by its id, with the field values it prefills; find the id with issue_templates_get_all. The issue body is in fieldTemplates.description, not the template's own description.

Get the comment templates configured in Yandex Tracker - the wording a team reuses when replying, with the users and mailing lists such a comment summons. Read one before adding a comment. Pass queue for the templates of that queue plus those bound to no queue. All pages are fetched by default; pass page for a single one.

Get a single Yandex Tracker comment template by its id, including the comment text it inserts. Use comment_templates_get_all first to find the template id.

Get the agile boards (in russian - 'доски') of the organization; pass queue for the boards collecting issues of that queue. Matching is done on the board's own filter, so boards filtering by something else are missed - read a few issues with issues_find and look at their boards field for those.

Get a single Yandex Tracker agile board (in russian - 'доска') with its settings, columns, the field issues are estimated by and the working calendar. autoFilterSettings is the board's own filter and tells which issues it collects - read it to learn which queue a board is about.

Get the columns of a Yandex Tracker agile board with the issue statuses mapped onto each - use it to see which status an issue needs to show up in a given column. Richer than the columns in boards_get_all / board_get, which carry no statuses.

Get all sprints (in russian - 'спринты') of a specific Yandex Tracker agile board. The currently running sprint is the one with status 'in_progress'. Use the returned sprint id to put an issue into a sprint with the issue_create or issue_update tools.

Get one Yandex Tracker queue component (in russian - 'компонент') by its numeric id, with queue, lead, assignAuto and the version that component_update takes. Ids come from queue_get_components or an issue's components field.

Read one Yandex Tracker issue (task, ticket, bug; in russian - 'задача') by its key and return its full record, the current version included. To search instead, use issues_find. Comments, links, attachments, worklogs, checklist, changelog and transitions each have their own issue_get_* tool.

Get a page of comments of a Yandex Tracker issue by its id. Returns the comments plus next_cursor - pass it back as cursor until it is null.

Get a Yandex Tracker issue related links to other issues by its id

Find Yandex Tracker issues matching a Yandex Tracker Query (YQL) - not limited to queue/date, any indexed field can be used (assignee, status, tags, etc., see the query parameter for the full syntax).

Get the count of Yandex Tracker issues matching a query.

Get worklogs of a Yandex Tracker issue by its id

Get attachments of a Yandex Tracker issue by its id

Get checklist items of a Yandex Tracker issue by its id

Get possible status transitions for a Yandex Tracker issue. Returns list of available transitions that can be performed on the issue.

Get the change history (changelog) of a Yandex Tracker issue: status transitions, field edits (who changed what from -> to and when), comment changes and executed triggers. Returns a page of entries plus next_cursor - pass it back as cursor until it is null.

Get information about user accounts registered in the organization.

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.

Get information about a specific user by login or UID

Get information about the current authenticated user

Create a new version in a Yandex Tracker queue.

Create a component (in russian - 'компонент') in a Yandex Tracker queue - a label grouping the queue's issues by product, process or owner; lead is a user login.

Change the name, description, lead or auto-assign flag of a Yandex Tracker queue component (in russian - 'компонент'); omitted fields keep their value, clear_lead removes the lead.

Delete a Yandex Tracker queue component (in russian - 'компонент') by its numeric id. Cannot be undone.

Attach a local file to a Yandex Tracker issue. Pass the absolute path to a file readable on the MCP server host; the file is uploaded as multipart/form-data. Max file size 8 MB. Returns the created attachment.

Execute a status transition for a Yandex Tracker issue. Call issue_get_transitions first and pass one of the ids it returned - the API rejects anything else. Returns the transitions available in the new status.

Close a Yandex Tracker issue with a resolution: finds a transition to a 'done' status and executes it. The resolution has to be one the issue's type allows - read the type with issue_get, then call queue_get_metadata with expand=['issueTypesConfig'] for the resolutions of that type. Returns the transitions available in the new (closed) status.

Create an issue (in russian - 'задача') in a Yandex Tracker queue. There is no template argument: read a template with issue_templates_get_all and copy its fieldTemplates values into these arguments field by field. The returned version goes stale at once, as queue triggers bump it - re-read it with issue_get.

Update an existing Yandex Tracker issue. Only the parameters you pass change; the rest stay as they are. Use queue_get_fields to discover the queue's fields. version is optional optimistic locking - pass one read moments earlier with issue_get, never the one issue_create returned, since triggers bump it right after creation.

Add a worklog entry (log spent time) to a Yandex Tracker issue

Update a worklog entry (spent time record) in a Yandex Tracker issue

Delete a worklog entry (spent time record) from a Yandex Tracker issue

Add a comment to a Yandex Tracker issue. There is no template_id parameter: check comment_templates_get_all (with queue set) first and copy the template's template text into text and its summonees into the parameters below. To mention or call people so they get notified, use summonees - '@login' in the text notifies nobody.

Update an existing comment in a Yandex Tracker issue. To mention or call people, use summonees, not '@login' in the text.

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.

Delete a comment from a Yandex Tracker issue

Create a link between a Yandex Tracker issue and another issue. relationship reads from the current issue: 'depends on' means issue_id depends on the linked issue, 'is dependent by' is the reverse, 'relates' is a plain connection.

Delete a link between a Yandex Tracker issue and another issue. Use issue_get_links to retrieve the link IDs for an issue.

Add one or more items to the checklist of a Yandex Tracker issue. The checklist is created if the issue does not have one yet, and items are appended in the order given. Returns the issue's checklist after the items were added.

Update one checklist item of a Yandex Tracker issue - to check it off, rename it, or set an assignee or a deadline. Only the fields you pass change, and null leaves a field as it is: use clear_assignee / clear_deadline to remove a value. Item ids come from issue_get_checklist. Returns the whole checklist.

Delete a single item from the checklist of a Yandex Tracker issue. Use issue_get_checklist to get the item IDs. Returns the issue's checklist after the deletion.