coolify-mcp
Related Servers
Alternatives to coolify-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Coolify infrastructure management, providing 45 tools for servers, applications, databases, deployments, and diagnostics via natural language.7 npmMIT
- FlicenseBqualityDmaintenanceA unified MCP server for managing hosting fleets, enabling natural language control over SSH, WordPress, Cloudflare, MySQL, GitHub, Docker, Coolify, and more.381-
- AlicenseBqualityDmaintenanceMCP server that integrates with Coolify to let AI assistants manage Coolify instances via a clean toolkit wrapping the official REST API.35164 npm7MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to manage infrastructure, applications, databases, and services through the Coolify PaaS platform.6 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Coolify API integration, enabling management of applications, databases, services, servers, and deployments via Claude Code or any MCP-compatible client.5 npm2MIT
- AlicenseAqualityAmaintenanceOne MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.1932 npmMIT
TDQS
Scored across 116 tools
Tools are consistently prefixed by resource type (e.g., coolify_application, coolify_database), making them distinct within their sub-domains. However, the duplication of storage, env, and backup operations across applications, databases, and services creates some ambiguity; an agent might struggle to pick between similar tools for different resources without careful context management.
All 116 tools follow a flawless coolify_<resource>_<action> snake_case pattern (e.g., coolify_list_applications, coolify_create_database, coolify_delete_service_env). The naming is highly predictable, with consistent verbs like list, create, get, update, delete, start, stop, and restart applied uniformly across resource types.
At 116 tools, the count is at the high end, but it is justified by the comprehensive management of a complex PaaS platform covering applications, databases, services, servers, projects, teams, and more. The weight is noticeable, yet each tool serves a clear purpose, and the set would be incomplete without many of these operations.
The tool surface is extraordinarily complete, covering CRUD operations for all major resources (applications, databases, services, servers, projects, environments, private keys, GitHub apps, teams). It also includes lifecycle management (start, stop, restart), environment variables, storage, backups, scheduled tasks, deployments, logs, and health checks. There are no obvious operational gaps for managing a Coolify instance.