F
licenseA
qualityC
maintenanceConnects 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
-
ado-mcp-server
Related Servers
Alternatives to ado-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceEnables users to securely connect Claude Desktop to Azure DevOps for managing work items, metadata, comments, pull requests, and code reviews.15-
- FlicenseAqualityDmaintenanceBridges Claude Code with an on-premise Azure DevOps Server / TFS collection, enabling work item and Git operations via PAT authentication.121-
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with an on-premise Azure DevOps Server 2022, allowing users to list, view, create, and update work items through natural language.4MIT
- AlicenseNot gradedqualityBmaintenanceBrings on-premises Azure DevOps Server (including TFVC) to AI assistants with 49 tools for work items, repositories, pipelines, test plans, and wiki, along with profile-based secrets and write safety layers.43 npm13MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps for managing work items, repositories, wikis, and automating development workflows.MIT
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