awesome-coolify-mcp
Related Servers
Alternatives to awesome-coolify-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables managing multiple self-hosted Coolify instances via MCP, with tools for deploying, monitoring, and emergency operations.MIT
- AlicenseBqualityBmaintenanceMCP server for managing Coolify instances, enabling control of applications, databases, services, servers, and more via natural language.11623 npmMIT
- AlicenseAqualityBmaintenanceMCP server for managing a self-hosted Coolify instance. Provides full REST CRUD, deploy/watch capabilities, and an optional host-ops tier for live log streaming, SSH, Docker, and database access.2210 npmMIT
- AlicenseNot gradedqualityAmaintenanceFleet-level MCP server for Coolify that supports multiple instances and teams from one connection, with full REST API coverage and cross-instance search.1 npm5MIT
- AlicenseBqualityAmaintenanceMCP server for Coolify API that enables full deployment workflows from zero to production, including project, server, and application management.6582 npm3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Coolify API integration, enabling management of applications, databases, services, servers, and deployments via Claude Code or any MCP-compatible client.2 npm2MIT
TDQS
Scored across 19 tools
While each tool targets a distinct domain (applications, databases, servers, etc.), there is notable cross-tool overlap: multiple tools expose `logs` actions (application, deployment, diagnose), and `version` appears in both `system` and `meta`. Also, `resource.list/find` competes with domain-specific listing tools, creating potential for agent misselection.
All tool names are lowercase nouns in a consistent singular style (application, private_key, environment), and actions follow a predictable verb pattern (get, list, create, update, delete, start, stop, restart, deploy). Child actions use a uniform colon syntax (envs:list, backup:now), with no mixed casing or stylistic chaos.
With 19 tools, the server is in the 'heavy but reasonable' range. Each tool addresses a meaningful aspect of Coolify administration, though some could be consolidated (e.g., meta/system overlap, resource vs domain-specific lists). The count is not excessive given the domain's complexity.
The tool surface covers a broad range of Coolify resources, including applications, services, databases, servers, projects, environments, private keys, and deployments. Minor gaps exist, such as no update action for environments and no application backup actions (database backups are covered), but these are workaround-able and core workflows are well supported.