Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-resourcesB | Retrieve a comprehensive list of all resources managed by Coolify. This includes applications, services, databases, and deployments. |
| list-applicationsB | Fetch a list of all applications currently managed by Coolify. This provides an overview of all deployed applications. |
| get-applicationA | Retrieve detailed information about a specific application using its UUID. This includes the application's status, configuration, and deployment details. |
| start-applicationC | Start a specific application using its UUID. This initiates the application and makes it available for use. |
| stop-applicationB | Stop a specific application using its UUID. This halts the application and makes it unavailable. |
| restart-applicationA | Restart a specific application using its UUID. This stops and then starts the application, applying any configuration changes. |
| list-servicesB | Retrieve a list of all services managed by Coolify. This includes external services and microservices. |
| list-databasesA | Fetch a list of all databases managed by Coolify. This provides an overview of all database instances. |
| list-deploymentsB | Retrieve a list of all running deployments in Coolify. This includes details about the deployment status and history. |
| deployC | Deploy an application or service using a tag or UUID. This allows you to deploy new versions or updates to your applications. |
| update-applicationC | Update the settings of a specific application, such as health check configurations. This allows you to modify the application's behavior and monitoring settings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is some overlap between list-applications and list-resources, as list-resources includes applications along with other resources, which could cause confusion about which to use for listing applications. The application lifecycle tools (start, stop, restart, update) are clearly differentiated from each other and from retrieval tools.
All tool names follow a consistent verb-noun pattern using kebab-case, such as deploy, get-application, list-applications, restart-application, etc. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 11 tools, the count is well-scoped for managing applications and resources in a deployment platform like Coolify. Each tool serves a clear purpose, covering deployment, retrieval, listing, and lifecycle management without being overly sparse or bloated.
The tool set provides strong coverage for application management, including CRUD-like operations (deploy, get, update, start/stop/restart) and listing functions. However, there are minor gaps, such as no tools for creating or deleting databases or services, which might be expected in a full resource management suite, though the focus seems to be on applications.