Yandex Tracker MCP
未认领Yandex Tracker MCP Server with OAuth2 support
安装
claude mcp add yandex-tracker docker "run --rm -i -e TRACKER_TOKEN=your_tracker_token_here -e TRACKER_CLOUD_ORG_ID=your_cloud_org_id_here -e TRACKER_ORG_ID=your_org_id_here -e TRANSPORT=stdio ghcr.io/更多Developer Tools服务器
浏览完整目录安全概况
已认领和已认证的服务器每周接受一次静态扫描，显示代码能触及的范围（外部服务、环境变量、shell 命令、代理配置目录）以及带有已知公告的依赖。认领此列表即可获得。 安全概况的工作原理
67 个工具中显示 67 个
文档中列出的工具 (67)
内容来自项目文档。服务器握手不会验证每个工具的说明或行为。
Arguments.
Reads take entityid and fields; the find tools take input, filter, orderby, orderasc, rootonly, page, perpage. Create and update take summary (required on create), description, lead, teamusers, clients, followers, start (goals have none), end, tags, entitystatus, parententity, teamaccess and links,
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, inprogress, released, archived) and planned/actual dates
boards_get_all
The organization's agile boards; returns {boards, nextcursor}
comment_id
(int, required): Comment ID
comment_template_get
One comment template by id
comment_templates_get_all
The comment templates, with the template text and its summonees / maillistSummonees
component_create
Create a component in a queue
component_delete
Delete a component
component_get
One component with queue, lead, assignAuto and version
component_update
Change name, description, lead or auto-assign flag; omitted fields keep their value, clearlead removes the lead
due_date
(date, optional): Version due date in YYYY-MM-DD format
duration
(string, required): ISO-8601 duration (e.g. PT1H30M)
expand
(array of strings, optional): Fields to expand in the response. Available options: all, projects, components, versions, types, team, workflows, fields, issueTypesConfig
field
(string, optional): Filter the changelog by a field key (e.g. status)
fields
(optional): Fields to include in the response (e.g., ["key", "name"]). Helps optimize context window usage by selecting only needed fields. If not specified, returns all available fields.
followers
(array of IssueUpdateFollower, optional): Followers - array of objects with id (string, user ID or login)
get_global_fields
Every global field of the organization, with its schema and type
get_issue_types
Every issue type, for the type argument of issuecreate / issueupdate
get_priorities
Every priority, with id, key, name and order
get_resolutions
Every resolution, for the resolutionid of issueclose
get_statuses
Every issue status the organization defines
include_description
(boolean, optional, default: true): Whether to include issue description in the result. Can be large, so use only when needed.
include_local_fields
(boolean, optional, default: true): Whether to include queue-specific local fields
is_add_to_followers
(boolean, optional, default: true): Add comment author to followers
issue
(string, required): ID or key of the issue to link to (e.g. "TEST-123")
issue_add_comment
Add a comment; summonees is what notifies a user, an @login in the text notifies nobody
issue_add_link
Link two issues
issue_delete_comment
Delete a comment
issue_delete_link
Remove a link
issue_get
One issue by key: the full record, the current version included
issue_get_comments
A page of comments, oldest first; returns {comments, nextcursor}
issue_get_links
Links to related, blocking and duplicate issues
issue_get_url
The web URL of an issue
issue_get_worklogs
The time logged on one or more issues
issue_id
(string, format: "QUEUE-123")
issue_template_get
One issue template by id
issue_templates_get_all
The issue templates, with the fieldTemplates values they prefill; returns {values, hits, pages}
issue_update_comment
Edit a comment
link_id
(int, required): Link ID (as returned by issuegetlinks)
maillist_summonees
(array of strings, optional): Mailing lists to summon (emails)
markup_type
(string, optional): Use md for YFM (markdown)
parent
(IssueUpdateParent, optional): Parent issue reference with id (string) and/or key (string, e.g., 'QUEUE-123')
per_page
(optional): Number of items per page (default: 100)
priority
(string, optional): Priority key (from getpriorities tool)
queue
returns that queue's templates plus the ones bound to no queue, which are usable everywhere. TRACKERLIMITQUEUES applies: templates of a restricted queue are omitted from the listings and rejected on direct access, while templates without a queue stay visible.
queue_create_version
Create a version in the queue
queue_get_components
The queue's components as full objects, with lead, auto-assign flag and version; queuegetmetadata with expand: ["components"] gives ids and names only
queue_get_fields
The fields configured on the queue, local ones included; schema.required marks the mandatory ones
queue_get_metadata
Name, description, default type and priority, plus whatever expand asks for
queue_get_tags
The tags defined in the queue
queue_get_versions
The queue's versions, with dates and status
queue_id
(string, required): Queue key like "SOMEPROJECT"
queues_get_all
Every queue the token may see; returns {values, hits, pages}
relationship
(string, required): Link type describing how issueid relates to the linked issue. One of: relates, is dependent by, depends on, is subtask for, is parent task for, duplicates, is duplicated by, is epic of, has epic
resolution_id
(string, required): The resolution ID to set when closing (e.g., 'fixed', 'wontFix', 'duplicate')
sprint
(array of IssueUpdateSprint, optional): Sprint assignments - array of objects with id (int) field
summary
(string, required): Issue title/summary
summonees
(array of strings, optional): Users to summon (logins or IDs). This is the API way to mention/call users (notifications are triggered by this field, not by @login in text).
tags
(array of strings, optional): Issue tags
transition_id
(string, required): The transition ID to execute. IMPORTANT: Must be one of the IDs returned by issuegettransitions tool
user_get
One user by login or uid
user_get_current
The user the current token belongs to
users_get_all
A page of the organization's users; returns {values, hits, pages}
users_search
Find users by login, email or real name
worklog_id
(int, required): Worklog entry ID