M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAzure DevOps MCP ServerBring Azure DevOps projects, work items, repos, wikis, and pipelines to your AI agentGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS64 / 100 · C76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance16 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Teams already using Azure DevOps for work items, repos, wikis, or pipelines
  • Developers using VS Code with GitHub Copilot (or another MCP-capable client)
  • Scenarios wanting natural-language access to Azure DevOps without hand-writing REST API calls
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Teams not using Azure DevOps, or relying solely on GitHub or other project-management tools
  • Users wanting a minimal, zero-configuration server with no domain selection or account sign-in
  • Scenarios highly sensitive to breaking changes during preview — the README notes a recent full tool renaming/consolidation
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires OAuth browser sign-in with a Microsoft account matching the target Azure DevOps organization (remote and local)
  • Local server also supports authentication via --authentication azcli
  • Requires an Azure DevOps organization identifier (e.g. 'contoso')
  • Local mode can set default project and team via environment variables to skip selection prompts
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Broad tool surface may allow modifying organizational data such as wiki pages and work items — verify the signed-in account's permission scope
  • The remote server is in preview, with functionality and issue tracking still evolving
  • A recent full tool consolidation renamed existing tools, which can break existing agents/skills unless pinned to an older version or updated per docs/TOOLSET.md
  • The local server requires Node.js 20+; an unmet version requirement will cause install or runtime failures
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsVS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015