No user-submitted related servers found.
Scored across 81 tools
Several tools have near-identical or confusingly scoped names, such as get_work_item_types, list_work_item_types, and list_all_work_item_types, which can easily cause misselection. The work_item/workitem split across relation, attachment, and testcase tools further blurs boundaries, especially since descriptions are not always enough to distinguish them.
Most tools follow a predictable get/list/create/update/delete + noun pattern, which is helpful. However, there are notable inconsistencies: work_item is sometimes written as workitem, collection retrieval uses both get_ and list_ prefixes, and generic names like compare lack context.
81 tools is an extreme count for a single MCP server, even for a broad DevOps platform. The surface is too large for reliable agent tool selection and would be better split into focused servers or consolidated where tools are redundant.
Coverage is broad across code management, work items, sprints, versions, efforts, and organization data. However, there are notable lifecycle gaps such as no delete_sprint, no close/abandon change request operation, no project/program creation, and no delete operations for effort records or attachments.