Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Azure DevOps MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
      -

    • 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
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 46 tools

    Disambiguation3/5

    Most tools map to distinct resource-action pairs, but several near-duplicates create real confusion: get_project vs get_project_details, get_repository vs get_repository_details, and get_wikis vs get_wiki_page vs list_wiki_pages. Users will often need to inspect descriptions closely to pick the right

    Naming Consistency4/5

    The naming is overwhelmingly consistent: snake_case verb_noun patterns like get_, list_, create_, update_, search_, and trigger_. Minor deviations include get_all_repositories_tree and pipeline_timeline, which break the verb-first pattern, but the convention is broadly predictable.

    Tool Count2/5

    At 46 tools, the surface is very large and likely overwhelming for users. Even though Azure DevOps is a wide domain, many tools could be consolidated or hidden behind parameters, and the count is well beyond the typical well-scoped range.

    Completeness3/5

    The toolset covers a broad range of Azure DevOps areas: projects, repositories, work items, pull requests, pipelines, and wikis. However, there are notable gaps such as no create/delete repository or project, no work item deletion, and no PR approval/rejection action, leaving some workflows incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources