
Coolify MCP
io.github.frndchagasPublished by GitHub account frndchagasv2.3.1Updated Oct 24, 2026
MCP server for Coolify API operations.
Overview
An MCP server that lets an assistant manage a Coolify instance: projects, servers, applications, databases, services, deployments and environment variables.
- What you can do
- List, create, update and delete projects, environments, servers, SSH keys and GitHub Apps, and inspect teams and server resources and domains. Create, configure, start, stop, restart and delete applications, including public git, GitHub App, deploy key, Dockerfile and Docker image sources. Manage databases across eight engines with backups and env vars, plus services, Docker Compose deployments, storages, scheduled tasks and previews. Trigger, cancel and inspect deployments, diagnose apps and servers, and get a one-call infrastructure overview. Manage environment variables with masking, and search the bundled Coolify documentation offline.
- When to use it
- Useful when you run Coolify and want an assistant to handle deployment work from the chat: standing up a project from scratch, checking why an app failed, restarting or redeploying services, or adjusting environment variables and backups without clicking through the dashboard.
- Requirements
- Runs locally over stdio via the npm package, needing Node 18+. Requires a Coolify API base URL in COOLIFY_BASE_URL and an API token from the Coolify dashboard in COOLIFY_TOKEN. Network access to the Coolify instance. An optional HTTP transport exists with its own port and bearer token settings.
Installation
In SourceWeft
- Open Coolify MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
coolify-mcp
[npm version] [npm downloads] [license] [node version] [typescript] [CI] [Glama score]
MCP server for Coolify API - enables full deployment workflows from zero to production.
Targets the Coolify v4.3.10 API. Types and schemas are generated directly from Coolify's official OpenAPI spec, so tool inputs always match what the API actually accepts.
Features
- Full Deployment Workflow: Create projects, environments, servers, and applications from scratch
- 5 Application Types: one
createApplicationtool covers public git, GitHub App, Deploy Key, Dockerfile, and Docker Image sources — plus Docker Compose deployments viacreateService(since Coolify v4.1, compose deployments are services) - Environment Management: Full CRUD for environment variables with secret masking
- Deployment Control: Deploy (optionally waiting for the terminal status, with a log tail on failure), start, stop, restart applications
- Diagnostics:
diagnoseAppfinds an app by UUID, name, or domain and aggregates status, recent deployments, failure log tails, runtime logs, and suggested next actions - Docs Search:
searchDocsruns full-text search across the official Coolify documentation from a bundled local index — no network needed - Security: Write protection, secret redaction, and MCP annotations (
readOnlyHint/destructiveHint) so clients can auto-approve reads and gate destructive calls - Near-full API coverage: databases (8 engines, backups, envs), services, storages, scheduled tasks, teams, previews, servers, SSH keys, and GitHub Apps
- Token-efficient: 65 tools whose definitions cost ~9k tokens of context, with strict runtime validation against schemas generated from Coolify's OpenAPI spec
Requirements
- Node 18+
- A Coolify API token (Settings > API in your Coolify dashboard)
Install
Claude Desktop, one-click: download coolify-mcp.mcpb from the latest release and drag it into Settings → Extensions. You'll be prompted for your Coolify URL and token — no Node install, no JSON editing.
Via npm:
Quick Start
Claude Code CLI
OpenAI Codex CLI
Or edit ~/.codex/config.toml:
Manual Configuration (~/.mcp.json)
Environment Variables
Deploy from Zero
With this MCP, you can deploy an application from scratch:
Tools Reference
Projects & Environments
Servers & Infrastructure
Applications - Read
Applications - Create
Docker Compose deployments are created with
createServicepassingdocker_compose_raw— since Coolify v4.1 they are services, not applications.
Applications - Manage
Environment Variables
Database and service env vars have their own tools:
databaseEnvsandserviceEnvs.
Deployments
Databases
Services
Storages, Scheduled Tasks & Previews
Teams, Servers & Git
Batch Operations
Other
Security Features
Write Protection
Disable all write operations:
Secret Masking
- Environment variable values are masked by default
- Database credentials are redacted
- Use
showSecrets: trueonly when necessary
HTTP Transport Hardening
The HTTP transport binds to 127.0.0.1 by default. To expose it beyond loopback, set MCP_HTTP_TOKEN — every request to /mcp must then carry Authorization: Bearer <token> (checked in constant time) — and the bind switches to 0.0.0.0 (override with MCP_HTTP_HOST). Binding to a non-loopback host without a token logs a loud warning: anyone who can reach the port controls your Coolify instance.
Human Confirmation on Destructive Deletes
On MCP clients that support elicitation (Claude Code, VS Code Copilot), deleting a project, application, database, service, server, or private key asks you to confirm first, stating what will be lost. Clients without elicitation behave exactly as before. A decline, cancel, or timeout aborts the call; set COOLIFY_MCP_ELICITATION=off to disable the prompts entirely.
Development
Scripts
Pinned Coolify Version
Version is defined in src/coolify/constants.ts. To update:
- Edit
COOLIFY_VERSIONinsrc/coolify/constants.ts - Run
npm run generate
Registry Listings
- MCP Registry:
io.github.frndchagas/coolify-mcp
MCP Client Examples
HTTP Client
Stdio Client
License
MIT
Source: README.md at commit c06fd15
Tools
0Version history
1- v2.3.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts