Skip to main content
Glama
Sign In
isaacOjeda

Azure DevOps MCP

by isaacOjeda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Azure DevOps MCP

No user-submitted related servers found.

    Related Servers

    • ado-mcp-server

      andrelopes-code
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code to interact with Azure DevOps Server on-premises (work items, pull requests, repositories) through secure, controlled, safe-by-default access with read-only mode and explicit write confirmations.
      22
      MIT

    • azdo-mcp

      recepkucukekiz
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to Azure DevOps so it can read work items, repositories, files and pull request details, search and run WIQL queries, and, when write access is enabled, create or update work items, add comments, link items and open pull requests. Runs locally over stdio with a personal access token, Azure CLI credentials, or a read-only mode that exposes only the lookup tools.
      25 npm
      MIT

    • MCP Azure DevOps Server

      AthosSchrapett
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Azure DevOps for managing work items, pull requests, and pipelines through natural language.
      19 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources