No user-submitted related servers found.
Scored across 15 tools
Tools split cleanly by resource (work items vs pull requests) and action (list/get/query/create/update/add). Work item query vs get are distinct via WIQL vs ID lookup, and metadata tools are clearly scoped. No two tools appear to do the same job.
All tools follow the ado_<resource>_<action> pattern, which is predictable and easy to learn. Minor inconsistencies exist: list/query sometimes use plural resources (pull_requests_list, work_items_query) while other actions use singular forms, and both 'add' and 'create' are used for different resources.
15 tools is at the upper boundary but remains well-scoped for work-item and pull-request workflows. Each tool maps to a distinct operation, and the metadata tools (types/fields) are justified by Azure DevOps's dynamic work-item models.
Work item coverage is solid with query/get/create/update/comments, but the PR side lacks update/complete/abandon operations, so a PR can be created and discussed but not merged or completed through the server. There is also no work-item delete or reply to existing PR review threads. These are notable lifecycle gaps rather than trivial workarounds.