Skip to main content
Glama

Related Servers

Alternatives to MCP Azure DevOps Server

No user-submitted related servers found.

    Related Servers

    • 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
      69 PyPI
      79
      MIT
    • 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
      -
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI agents to interact with Azure DevOps wikis, providing capabilities for content search, page management, and hierarchical structure navigation.
      5
      7 npm
      MIT
    • -
      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
      -

    TDQS

    B3.1/5.0

    Scored across 37 tools

    Disambiguation3/5

    The tool set shows clear grouping into wikis, work items, and general operations, but there is significant overlap within the wiki category (e.g., create_wiki_page, create_or_update_wiki_page_smart, update_wiki_page, update_wiki_page_safe) that could cause confusion about which tool to use for specific scenarios. The work item tools are better distinguished, with clear purposes for creation, retrieval, updating, and deletion.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., create_wiki, delete_work_item, get_projects), which aids predictability. However, there are minor deviations like create_or_update_wiki_page_smart (longer name with 'smart' suffix) and server_health_check (uses underscore but deviates from the typical action-object pattern), slightly reducing consistency.

    Tool Count2/5

    With 37 tools, the count is excessive for an Azure DevOps server, leading to potential overwhelm and redundancy. While Azure DevOps is a broad platform, the tool set includes many specialized or overlapping tools (e.g., multiple wiki update methods) that could have been consolidated, making it feel heavy and less scoped.

    Completeness4/5

    The tool set provides comprehensive coverage for wikis and work items, including CRUD operations, search, and advanced features like state transitions and batch operations. Minor gaps exist, such as lack of tools for repository management beyond listing and file content retrieval, but core workflows for the covered domains are well-supported.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing