Skip to main content
Glama
jaybird-us

Azure DevOps MCP Server

by jaybird-us
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Azure DevOps MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Azure DevOps Server

      aadityasinghal7
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, providing capabilities for work item management, project management, and team collaboration through natural language.
      21
      -

    • MCP Azure DevOps Server

      Vortiago
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.
      21
      79
      MIT

    • Azure DevOps MCP Server

      kevinmeyvaert
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A reference server implementation for the Model Context Protocol that enables AI assistants to interact with Azure DevOps resources and perform operations such as project management, work item tracking, repository operations, and code search programmatically.
      7
      -

    • azure-devops-mcp

      RyanCardin15
      A
      license
      Not graded
      quality
      D
      maintenance
      This server provides a convenient API for interacting with Azure DevOps services, enabling AI assistants and other tools to manage work items, code repositories, boards, sprints, and more. Built with the Model Context Protocol, it provides a standardized interface for communicating with Azure DevOps
      40 npm
      58
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is potential confusion between 'get_work_item' and 'inspect_work_item' as both retrieve work item data, and between 'test_query' and 'query_work_items' as both involve querying. Overall, the set is well differentiated.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern in snake_case, e.g., 'create_work_item', 'list_projects', 'update_wiki_page'. Even 'healthcheck' is conventionally acceptable. The naming is uniform and predictable.

    Tool Count2/5

    With 41 tools, the count is well above the recommended range (3-15). While Azure DevOps is broad, many tools are administrative or discovery-only, leading to an excessive surface that may overwhelm agents.

    Completeness2/5

    Significant gaps exist: there are no tools to create, update, or delete projects, repositories, pipelines, or teams—only listing is supported. Work items lack deletion. This missing CRUD coverage leaves agents with dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources