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.

DimensionArgo CD MCP ServerAn MCP server for Argo CD, enabling AI assistants to interact with your Argo CD applications through natural language.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS71 / 100 · B76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions16 / 2014 / 20
Maintenance16 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • DevOps teams wanting to use AI assistants with Argo CD.
  • Users with GitOps workflows needing natural language management of Kubernetes applications.
  • Developers using MCP within VS Code or Cursor.
  • 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
  • Production environments with strict security boundaries that cannot expose API tokens to AI assistants.
  • Multi-replica deployments without sticky sessions unless running `--stateless` mode.
  • 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 access to the Argo CD API, including read permissions for clusters, applications, resource trees, logs, events, etc.
  • Write operations (create, update, delete, sync, run action) require appropriate Argo CD RBAC permissions.
  • The server reads API tokens from environment variables or HTTP headers, never exposing them in tool calls.
  • 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
  • API tokens are sensitive; must be stored securely and not leaked.
  • Write operations can modify or delete applications; use with caution.
  • Disabling TLS verification for self-signed certificates reduces security.
  • Default token is bound to the default base URL to prevent credential exfiltration, but misconfiguration can cause fail-closed behavior.
  • 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 clientsClaude Desktop, VS Code, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1415