Coolify Creation MCP
by donatas9898
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COOLIFY_URL | Yes | Your Coolify instance origin, for example https://coolify.example.com. /api/v1 is also accepted. HTTPS is required for remote instances; loopback HTTP is allowed for development. | |
| COOLIFY_TOKEN | Yes | Coolify API token for the team that owns the project, with read + write permissions. Deploy webhooks require a token with deploy permission. Configure this privately in your MCP host's secret configuration or inherited environment. | |
| COOLIFY_ALLOW_INSECURE_HTTP | No | Set to true to deliberately use remote HTTP instead of HTTPS. This sends credentials without encryption; only enable on a trusted network. | false |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues