No user-submitted related servers found.
Scored across 56 tools
Most tools are clearly separated by resource (issue, queue, component, board, user, comment, worklog, checklist) and action (get, create, update, delete, add, find). Some potential confusion exists between queue_get_components and component_get, or between issue_get and issues_find, but descriptions clarify the distinction well.
The naming pattern is mostly consistent: resource_action (e.g., issue_get, issue_create, component_delete, queue_get_versions). Minor deviations exist: issues_find and issues_count use plural resource, and issue_templates_get_all vs issue_template_get are slightly inconsistent, but overall the pattern is predictable.
56 tools is a large surface for a single MCP server, but Yandex Tracker is a broad platform covering issues, queues, components, boards, sprints, users, comments, worklogs, checklists, templates, and metadata. The count is heavy but each tool maps to a distinct operation; still, it exceeds the typical well-scoped range.
The tool set provides comprehensive CRUD and lifecycle coverage for issues, comments, worklogs, checklist items, components, and links, plus metadata discovery (fields, statuses, priorities, resolutions, templates, users, boards, sprints). The only minor gap is lack of direct issue deletion or board/queue creation, but those are rarely needed and the surface is otherwise complete.