Coolify Creation MCP
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
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 |
|---|---|
| get_creation_contextB | Inspect a project's environments and applications, plus available servers and destinations across the authenticated team. inventory_scope labels those boundaries. Returns selected fields without credentials. |
| plan_docker_image_applicationB | Validate a Docker Image application and show its creation request without writing. Checks project/environment, server/destination, and duplicate names. Git sources support Nixpacks, Railpack, static, Dockerfile, and Docker Compose builds. |
| create_docker_image_applicationB | Create one Docker Image application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying. |
| plan_public_repository_applicationB | Validate a public Git repository application and show its creation request without writing. Checks project/environment, server/destination, and duplicate names. Git sources support Nixpacks, Railpack, static, Dockerfile, and Docker Compose builds. |
| create_public_repository_applicationA | Create one public Git repository application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying. |
| plan_github_app_applicationB | Validate a private Git repository through a GitHub App application and show its creation request without writing. Checks project/environment, server/destination, and duplicate names. Git sources support Nixpacks, Railpack, static, Dockerfile, and Docker Compose builds. |
| create_github_app_applicationB | Create one private Git repository through a GitHub App application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying. |
| plan_deploy_key_applicationB | Validate a private Git repository through a deploy key application and show its creation request without writing. Checks project/environment, server/destination, and duplicate names. Git sources support Nixpacks, Railpack, static, Dockerfile, and Docker Compose builds. |
| create_deploy_key_applicationB | Create one private Git repository through a deploy key application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying. |
| plan_dockerfile_applicationA | Validate a inline Dockerfile application and show its creation request without writing. Checks project/environment, server/destination, and duplicate names. Git sources support Nixpacks, Railpack, static, Dockerfile, and Docker Compose builds. |
| create_dockerfile_applicationB | Create one inline Dockerfile application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying. |
| get_deployment_webhookA | Verify a team-owned application and return its deployment URL and required authentication, without triggering deployment or returning a token. |
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 12 tools
Each tool has a distinct action and application type. The plan_* and create_* pairs are clearly differentiated by validation versus writing, and the two get_* tools cover inventory and webhook retrieval.
All tool names follow a consistent snake_case verb_noun pattern: get_*, plan_*, and create_*. The application-type suffixes are predictable and readable.
Twelve tools are well-scoped for a creation-focused MCP. The plan/create pairs map cleanly to five supported application sources, with two supporting inspection tools.
The surface covers creation across Docker Image, public Git, GitHub App, deploy key, and inline Dockerfile applications, plus preflight context and webhook retrieval. It intentionally omits deployment triggering and update/delete operations, which are reasonable gaps for a creation-focused server but may limit follow-up workflows.