azure-devops-server-mcp
Related Servers
Alternatives to azure-devops-server-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables multiple users and hosted assistants to connect to a private Forgejo instance through OAuth or token pass-through, acting only with each user's own token permissions. Provides MCP tools to browse repositories, files, commits, issues, pull requests, actions, and releases, and to perform guarded writes such as creating issues, branches, files, and pull requests.Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.151MIT
- FlicenseNot gradedqualityFmaintenanceThis MCP server enables AI agents to create Pull Requests in a self-hosted Bitbucket Server instance.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access a unified registry of GitHub repositories and open pull requests across many users and organizations through a stdio MCP interface.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA remote multi-tenant MCP server that lets AI agents read repositories and create work branches with multi-file commits on Forgejo or Gitea instances, while leaving review and merging to a person and blocking destructive or administrative actions.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants such as Claude, Cursor, and Windsurf to GitHub repository intelligence, code review, AST-based code and security analysis, web and documentation search, and automated test and documentation generation through MCP tools.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource (server, repository, branch, PR read vs. PR write), and the `_write` suffix plus description clearly separates read from write for pull requests. The only mild overlap is repo_pull_request vs. repo_pull_request_write, which is mitigated by explicit read-only vs. create/update language.
The set follows a predictable domain-prefix + resource pattern (repo_repository, repo_branch, repo_pull_request, repo_pull_request_write). server_info is the lone outlier that drops the prefix, and some tools are dual-purpose rather than verb_noun, but overall it reads consistently.
Five tools is a tight, well-scoped surface for a read-mostly Azure DevOps Git/PR server. It is slightly lean, but each tool earns its place with no redundant entries.
Coverage is deliberately narrow: repositories and branches are read-only, PRs support create/update but no merge, comments, or completion, and there is no work item or pipeline support. The descriptions reference a list_projects capability that is not present as a tool, a notable gap for the stated discovery workflow.