Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.
- Home
- Top MCPs for Web Hosting
- Coolify
Coolify
Deploy to your own server from an agent — the self-hosted answer to Vercel and Railway.
Quick answer
What it does
Exposes the Coolify v4 API as MCP tools across projects, servers, applications, databases and deployments — application creation in five source flavours, lifecycle control (`start_application`, `stop_application`, `restart_application`), and `get_application_logs`.
Best for
- Deploying to your own VPS from an agent
- Creating apps from a Dockerfile or Compose file
- Restarting and reading logs without SSH
- Self-hosted or EU-data-residency requirements
Not for
- Teams with no server to run Coolify on
- Workflows needing vendor support on the MCP
Source: top-mcps.com/mcp/coolify — verified Sep 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "coolify": { "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export COOLIFY_BASE_URL=https://coolify.example.com # export COOLIFY_TOKEN=your_coolify_api_token claude mcp add coolify -- npx -y coolify-mcp-server@latestRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "coolify": { "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "coolify": { "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "coolify": { "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "coolify": { "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "-y", "coolify-mcp-server@latest" ], "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.coolify] command = "npx" args = [ "-y", "coolify-mcp-server@latest", ] env = { COOLIFY_BASE_URL = "${COOLIFY_BASE_URL}", COOLIFY_TOKEN = "${COOLIFY_TOKEN}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "coolify": { "command": { "path": "npx", "args": [ "-y", "coolify-mcp-server@latest" ] }, "env": { "COOLIFY_BASE_URL": "${COOLIFY_BASE_URL}", "COOLIFY_TOKEN": "${COOLIFY_TOKEN}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneCoolify doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
COOLIFY_BASE_URL,COOLIFY_TOKENin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
create_public_application | Create an application from a public Git repository. | — | Write |
create_private_github_app_application | Create an application from a private repo via a GitHub App. | — | Write |
create_dockerfile_application | Create an application from a Dockerfile, no Git required. | — | Write |
create_dockercompose_application | Create an application from a Docker Compose file. | — | Write |
get_application | Return one application by UUID. | — | Read |
update_application | Update an application by UUID. | — | Write |
delete_application | Delete an application by UUID. | — | Write |
start_application | Start an application. | — | Write |
stop_application | Stop a running application. | — | Write |
restart_application | Restart an application. | — | Write |
get_application_logs | Read application logs. | — | Read |
Security & scope
- Access scope
- Read + write
- Sandbox
- No sandbox. The token addresses a live Coolify instance and everything it manages.
- Gotchas
- `delete_application` is immediate and takes only a UUID. There is no confirmation and no soft delete.
- A Coolify API token is instance-wide — it reaches every project and server that instance controls, not one app.
- Tool names and required arguments were read from a probe with placeholder credentials. A real instance may expose additional tools; treat this list as a lower bound.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. web hosting work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-hosting
Compare Coolify MCP vs [Railway MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/coolify - top-mcps.com listing for Railway
Install the Coolify MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/coolify (fetch https://top-mcps.com/mcp/coolify.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (COOLIFY_BASE_URL, COOLIFY_TOKEN) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 1 update tracked.Refreshed install snippets and fact sheet; verified for 2026.
More Web Hosting MCPs
Other tools in the same category worth evaluating.
Deploy a site, read the build, and manage projects, forms and extensions with Netlify's official MCP server.
Provision Render services, read deploy logs and metrics, and query Postgres read-only — over a hosted OAuth MCP.
Compared with Coolify
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Web Hosting? See all Web Hosting MCPs →
