coolify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COOLIFY_TOKEN | Yes | Your Coolify API token in the format <id>|<secret> (both parts required, scope write + read:sensitive) | |
| COOLIFY_CONFIG | No | Path to a JSON config file (alternative to environment variables) | |
| COOLIFY_BASE_URL | Yes | The base URL of your Coolify instance (e.g. https://coolify.example.com) | |
| COOLIFY_SSH_HOST | No | Explicit SSH host/IP override for host-ops (takes precedence over auto-derivation) | |
| COOLIFY_SSH_PORT | No | SSH port override for host-ops | |
| COOLIFY_SSH_USER | No | SSH user override for host-ops | |
| COOLIFY_SSH_KEY_PATH | No | Path to the SSH private key for host-ops (e.g. ~/.ssh/id_ed25519) | |
| COOLIFY_PINNED_VERSION | No | Pin the Coolify version for version-specific behavior | |
| COOLIFY_SSH_HOST_SERVER | No | UUID or name of the Coolify control server (override when auto-match fails) | |
| COOLIFY_DB_READONLY_USER | No | Read-only PostgreSQL user for query_coolify_db tool | |
| COOLIFY_SSH_KEY_PASSPHRASE | No | Passphrase for the SSH private key | |
| COOLIFY_DB_READONLY_PASSWORD | No | Password for the read-only PostgreSQL user | |
| COOLIFY_SSH_KNOWN_HOSTS_PATH | No | Path to a known_hosts file for SSH (defaults to ~/.ssh/known_hosts) | |
| COOLIFY_SSH_KNOWN_HOST_FINGERPRINT | No | SHA-256 host fingerprint for SSH verification (alternative to known_hosts) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deployA | Trigger a new deployment for an application (by UUID or tag). Optionally force-rebuild or deploy a pull-request preview. FENCED: requires --allow-destructive and confirm:true (code/credential write). |
| get_deploymentsA | List active deployments (no args) or the deployment history for a specific application (app_uuid). Supports pagination with skip/take. |
| cancel_deploymentA | Cancel an in-progress deployment by its deployment UUID (fenced). Requires --allow-destructive and confirm:true. |
| deploy_watchA | Trigger a deployment and block until it reaches a terminal state (finished/failed/cancelled/skipped). Emits MCP progress notifications while polling. Returns per-resource final statuses and a logs tail on failure. FENCED: requires --allow-destructive and confirm:true (code/credential write). |
| list_resourcesA | List all Coolify resources (applications, databases, services) across all projects. Optionally filter by type. |
| get_resourceA | Get full details of a specific Coolify resource by type and UUID. |
| create_resourceA | Create a new Coolify resource. |
| update_resourceA | Update configuration fields of an existing Coolify resource. FENCED: requires --allow-destructive and confirm:true (fields can rewrite deploy/start commands — a code-execution write). Pass the fields to change in |
| control_resourceA | Start, stop (fenced), or restart (fenced) a Coolify resource. stop and restart are destructive — they require --allow-destructive and confirm:true. For applications, start/restart return a deployment_uuid that can be used to track progress. |
| delete_resourceA | Delete a Coolify resource permanently. Requires |
| manage_storageB | List, create, update, or delete persistent volume storage for an application, database, or service. For create/update, pass the storage fields in |
| manage_backupsA | List, create, update, or delete database backup schedules and executions. Only applicable to databases. For create/update, pass the schedule fields in |
| manage_scheduled_tasksA | List, create (fenced), update (fenced), delete (fenced), or view executions of scheduled tasks on an application or service. create and update are code-execution writes — they require --allow-destructive and confirm:true. |
| manage_envA | Manage environment variables for a Coolify resource (application, database, or service). action=list returns all vars with a redaction_hint when any value appears empty or masked. action=set upserts one var ({ key, value }) or many ({ vars: [{key,value},...] }) via bulk API. action=delete (fenced) removes a single var by its env_uuid (UUID returned from list); requires --allow-destructive and confirm:true. |
| get_logsA | Fetch a log snapshot for a Coolify resource. • application: uses GET /applications/{uuid}/logs?lines= (REST API). • database / service: requires --enable-host-ops; the docker logs fallback is wired in Task 31. |
| get_serversA | Query Coolify servers. Actions: list (summary fields by default; include:true for full), get, validate, resources, domains. |
| manage_serverC | Create, update, or delete (fenced) a Coolify server. |
| provision_hetznerA | Provision a new server on Hetzner Cloud via Coolify (destructive — creates billable infrastructure). Requires --allow-destructive flag and confirm:true. |
| hetzner_inventoryA | Browse Hetzner Cloud resource catalog exposed by Coolify. Use before provision_hetzner to pick a server type and location. |
| manage_keysA | Manage Coolify SSH private keys (security keys). Actions: list, get, create (fenced), update (fenced), delete (fenced). create and update are credential writes — they require --allow-destructive and confirm:true. Note: update uses a collection-level PATCH — uuid is passed in the body. |
| manage_projectsC | Manage Coolify projects and their environments. Actions: list, get, create, update, delete (fenced), list_environments, create_environment, get_environment, delete_environment (fenced). |
| list_instancesA | List the Coolify instances this server is configured to drive (names, base URLs, default, and per-instance host-ops/destructive flags). Never returns tokens or other secrets. Pass an instance name as the 'instance' arg to any other tool to route to it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jimrarras/coolify-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server