Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COOLIFY_API_URL | Yes | Your Coolify instance URL (include port if needed) | |
| COOLIFY_API_TOKEN | Yes | Your Coolify API token (generate in Coolify Settings > API) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| config-statusD | – |
| applicationsD | – |
| databasesD | – |
| servicesD | – |
| projectsD | – |
| serversD | – |
| deploymentsD | – |
| private-keysD | – |
| systemD | – |
| pingD | – |
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 10 tools
The tool names identify broad resource areas, but several overlap conceptually, such as services vs. applications and system vs. config-status. With no descriptions, agents have little basis to determine which tool is appropriate for a given task.
Most tool names follow a simple lowercase-hyphenated plural noun pattern, but there is no consistent verb-noun structure and there are outliers like ping, system, and config-status. The naming is readable but not a strong unified convention.
Ten tools is a reasonable count for a server focused on managing infrastructure resources. However, the lack of descriptions makes it difficult to confirm that each tool earns its place in the set.
The surface appears to be read-oriented resource access rather than full lifecycle coverage, with no obvious create, update, or delete operations. Tools like private-keys and config-status hint at configuration management, but the set likely leaves agents unable to perform common management workflows.