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
      D
      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
      49 PyPI
      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
      44 npm
      60
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 49 tools

    Disambiguation3/5

    Many tools are distinct by resource and action (repositories, work items, PRs, wikis, pipelines), but several overlapping pairs create ambiguity: get_project_details vs get_project, get_repository_details vs get_repository, get_file_content vs tree tools, and create_wiki_page (which also updates) vs update_wiki_page. Descriptions help clarify, but the boundaries are not consistently sharp.

    Naming Consistency4/5

    Most tools follow a predictable snake_case verb_noun pattern (list_repositories, get_work_item, create_pull_request, update_wiki_page). Minor deviations exist, such as pipeline_timeline lacking a verb and get_wikis vs list_wiki_pages, but the overall convention is readable and mostly consistent.

    Tool Count2/5

    49 tools is excessive for a single MCP server, far beyond the 3-15 well-scoped range and even beyond the 16-25 heavy range. Azure DevOps is broad, but this surface would benefit from consolidation or grouping.

    Completeness3/5

    The server covers many core read/write operations across repositories, work items, PRs, wikis, and pipelines. However, notable lifecycle gaps remain: no delete_work_item, no PR merge/abandon/complete operation, no repository create/delete, no wiki page delete, and no pipeline cancel/update.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources