Yandex Tracker MCP

queue_get_metadata

with expand: ["issueTypesConfig"] is where the resolutions valid for each issue type come from - issue_close needs one of them.

TRACKER_LIMIT_QUEUES

and TRACKER_READ_ONLY_QUEUES apply through the component's queue: component_update and component_delete read the component first to learn it, and a component…

Arguments.

Reads take entity_id and fields; the *_find tools take input, filter, order_by, order_asc, root_only, page, per_page.

users_search

matches login and email exactly first and falls back to fuzzy name matching (80% similarity, at most the three best matches).

queue

returns that queue's templates plus the ones bound to no queue, which are usable everywhere.

fields

uses Tracker's own spelling (storyPoints, not story_points) and accepts any field name, a queue's local and the organization's custom fields included - pass…

include_description

is ignored when description is listed in fields: naming it there is an explicit request for it.

per_page

defaults to 100 and can be lowered when a page does not fit the context window.

queues_get_all

Every queue the token may see; returns {values, hits, pages}

queue_get_tags

The tags defined in the queue

queue_get_versions

The queue's versions, with dates and status

queue_get_components

The queue's components as full objects, with lead, auto-assign flag and version; queue_get_metadata with expand: ["components"] gives ids and names only

queue_create_version

Create a version in the queue

queue_get_fields

The fields configured on the queue, local ones included; schema.required marks the mandatory ones

component_get

One component with queue, lead, assignAuto and version

component_create

Create a component in a queue

component_update

Change name, description, lead or auto-assign flag; omitted fields keep their value, clear_lead removes the lead

component_delete

Delete a component

users_get_all

A page of the organization's users; returns {values, hits, pages}

user_get

One user by login or uid

user_get_current

The user the current token belongs to

get_global_fields

Every global field of the organization, with its schema and type

get_statuses

Every issue status the organization defines

get_issue_types

Every issue type, for the type argument of issue_create / issue_update

get_priorities

Every priority, with id, key, name and order

get_resolutions

Every resolution, for the resolution_id of issue_close

issue_templates_get_all

The issue templates, with the fieldTemplates values they prefill; returns {values, hits, pages}

issue_template_get

One issue template by id

comment_templates_get_all

The comment templates, with the template text and its summonees / maillistSummonees

comment_template_get

One comment template by id

boards_get_all

The organization's agile boards; returns {boards, next_cursor}

board_get

One board with autoFilterSettings (what it collects), estimateBy, useRanking and its working calendar

board_get_columns

The board's columns with the issue statuses that land in each

board_get_sprints

The board's sprints with status (draft, in_progress, released, archived) and planned/actual dates

issue_get

One issue by key: the full record, the current version included

issue_get_url

The web URL of an issue

issue_get_comments

A page of comments, oldest first; returns {comments, next_cursor}

issue_add_comment

Add a comment; summonees is what notifies a user, an @login in the text notifies nobody

issue_update_comment

Edit a comment

issue_delete_comment

Delete a comment