Skip to main content
Glama
andrelopes-code

ado-mcp-server

by andrelopes-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ado-mcp-server

No user-submitted related servers found.

    Related Servers

    • tfs-mcp-server

      rickey-cpu
      F
      license
      A
      quality
      C
      maintenance
      Connects Claude to on-premise TFS (Team Foundation Server) via REST API, enabling read/write of work items, backlogs, sprints, and pull requests without manual copy-paste.
      8
      -

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

    • ADO Guard MCP

      abdulbasit7010
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants such as Claude, VS Code Copilot and Cursor to browse and modify Azure DevOps projects, work items, pull requests and pipelines through the Azure DevOps REST API, with a policy engine enforcing read-only defaults, dry-run diffs, one-time human approval tokens, project/branch scoping, secret redaction, rate limits and an audit log. Write and destructive operations stay gated behind explicit configuration and user confirmation, so agents can work with boards and pipelines without being handed full credentials.
      9
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Tools are clearly grouped by domain prefix (wit_, pr_, repo_, branch_, commit_, project_) and each maps to a distinct resource or action. The only mild ambiguity is wit_comments (read) vs wit_comment (write), but their descriptions clearly separate discussion reading from comment posting.

    Naming Consistency4/5

    The snake_case domain-prefixed naming is consistent and predictable overall, but verb placement varies: reads use both generic verbs (wit_get, pr_get) and resource nouns (wit_comments, wit_history, repo_list). This is a minor deviation rather than a chaotic mix.

    Tool Count3/5

    At 22 tools, the server sits in the heavy 16-25 band, though the count is partially justified by covering work items, PRs, repos, branches, commits, and projects. Each tool appears non-redundant, so the set is broad rather than bloated.

    Completeness3/5

    Work item coverage is strong: query, get, tree, comments, history, meta, create, update, link/unlink, comment, and attach are all present. However, the PR lifecycle has a notable gap: pr_update explicitly cannot change status and there is no merge or abandon tool, leaving PRs incomplete after creation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources