No user-submitted related servers found.
Scored across 55 tools
Most tools are clearly separated by resource and action (queues, boards, issues, components, users, templates). 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 mostly follows a consistent resource_action pattern (e.g., issue_get, issue_create, issue_update, queue_get_components). Minor deviations exist: issues_find vs issue_get, issues_count, get_priorities, get_statuses, get_issue_types, get_global_fields, get_resolutions, users_get_all vs user_get, and board_get_sprints vs boards_get_all.
55 tools is on the heavy side, but the server covers a broad domain (queues, boards, issues, components, users, templates, worklogs, checklists, links, transitions). The count is justified by the breadth, though it approaches the upper limit of what an agent can comfortably navigate.
The tool surface is remarkably complete: full CRUD for issues, comments, worklogs, checklist items, components, links, and versions; plus metadata discovery (fields, statuses, resolutions, priorities, templates, transitions). No obvious dead ends—every returned ID has a corresponding tool that consumes it.