Skip to main content
Glama
Sign In
ado-mcp-server

ado-mcp-server

by ms31376
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ado-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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.
      14 npm
      MIT

    • ado-mcp-server

      andrelopes-code
      A
      license
      B
      quality
      C
      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

    • azure-devops-local-mcp

      Laonnda
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.
      30
      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

    C2.6/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools are clearly separated by Azure DevOps subdomain and action: work items, pipelines, repositories, tests, teams. There is minor overlap between search_work_items, search_test_cases, and query_wiql as multiple search entry points, but the descriptions generally make the intended use clear.

    Naming Consistency4/5

    The set uses a consistent snake_case verb_noun pattern such as get_work_item, list_pipeline_runs, and search_test_cases. whoami is the only meaningful deviation, but it is a conventional identity command and remains understandable.

    Tool Count2/5

    At 28 tools, the surface is heavy and exceeds the well-scoped range, even for a broad platform like Azure DevOps. While many tools serve distinct domains, the total volume increases selection burden for an agent.

    Completeness2/5

    The surface is almost entirely read-only: there are no create, update, delete, queue-pipeline, or PR mutation operations. Even if read-only inspection is intentional, notable read gaps remain such as PR file/thread details and repository code search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources