No user-submitted related servers found.
Scored across 17 tools
Most tools map cleanly to distinct Azure DevOps resources and actions: projects, repositories, pull requests, work items, and pipelines. The main potential confusion is between ado_config and ado_context, since both describe profile/target resolution behavior, but their descriptions draw a reasonable boundary.
Tools consistently use the ado_ prefix and a predictable domain/action style, such as ado_pull_request_get and ado_work_item_update. There are minor deviations: collection tools use plural nouns with _list/_query, while individual-resource tools use singular nouns, and ado_config/ado_context omit an action verb.
Seventeen tools is slightly above the typical 3-15 range, but the server covers several distinct Azure DevOps domains: configuration/context, projects, repositories, pull requests, work items, and pipelines. The count is defensible and each tool appears to serve a specific purpose.
Core read and some write operations are present for pull requests, work items, and pipelines, but there are notable lifecycle gaps. Pull request merge/completion is explicitly unsupported, repositories and projects only have list operations, and pipeline actions such as cancel/update are missing.