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.

DimensionCoolify MCP ServerMCP server for managing self-hosted PaaS Coolify with 44 optimized tools.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS68 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions15 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers and DevOps professionals using Coolify for self-hosted PaaS.
  • Teams looking to simplify daily deployment and operations with AI assistants.
  • Scenarios involving multiple Coolify instances.
  • 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
  • Users without a Coolify instance.
  • Operations that need fully automated destructive actions without confirmation (though you can disable confirmations with COOLIFY_MCP_ELICITATION=off).
  • Deployments to incompatible Coolify versions (only v4.0 and above supported).
  • 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 a Coolify API access token (COOLIFY_ACCESS_TOKEN); its permissions determine what operations the MCP can perform.
  • Can read and modify resources such as apps, databases, services, and environment variables.
  • Destructive operations (e.g., delete, stop) trigger human confirmation unless disabled.
  • 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
  • If the API token has excessive permissions, unexpected deletion or stopping of resources could occur.
  • Destructive operations may cause data loss, but the confirmation mechanism reduces risk.
  • Sensitive information (like passwords and keys) is masked by default, but enabling reveal could pose a leak risk.
  • 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, Claude Code, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools4415