MCP Servers

awesome-coolify-mcp

Enables managing multiple self-hosted Coolify instances via MCP, with tools for deploying, monitoring, and emergency operations.

README

<h1 align="center">awesome-coolify-mcp</h1>

One MCP server. Every self-hosted Coolify instance you own. Verify connectivity, discover your fleet, deploy, tail logs, diagnose incidents, and run gated emergency ops — straight from Cursor, Claude, VS Code, Windsurf, or any MCP-speaking agent.

<a href="README.de.md">🇩🇪 Deutsch</a> · <a href="https://coolify.io">Coolify</a> · <a href="https://modelcontextprotocol.io">Model Context Protocol</a> · <a href="https://clezcoding.github.io/awesome-coolify-mcp/install.html">Install configurator ↗</a>

<a href="#-overview">Overview</a> · <a href="#-why-awesome-coolify-mcp">Why</a> · <a href="#-features">Features</a> · <a href="#-how-it-works">Architecture</a> · <a href="#-quick-start">Quick start</a> · <a href="#-install">Install</a> · <a href="#-tools-reference">Tools</a> · <a href="#-safety-model">Safety</a> · <a href="#-coming-soon">Roadmap</a>

One click installs with placeholder credentials — see <a href="#-install">Install</a> for the full walkthrough, or use the <a href="https://clezcoding.github.io/awesome-coolify-mcp/install.html">browser configurator</a> to fill in real values safely.

📋 Table of contents

Overview
Why awesome-coolify-mcp
Features
How it works
Quick start
Install
Supported clients
Environment variables
Tools reference
Safety model
Structured errors & retries
Example agent workflows
Status today
Coming soon
Local development
Links

🔭 Overview

Self-hosted Coolify is one of the best open-source alternatives to Heroku/Vercel-style PaaS platforms — but wiring it up to an AI coding agent has historically meant piecing together several small, overlapping community MCP integrations, each with its own schema, its own error format, and its own idea of what "safe" looks like.

awesome-coolify-mcp replaces that patchwork with a single, community-maintained MCP server that speaks Coolify's REST API 4.1.x through a clean, action-based tool surface. Instead of memorizing dozens of near-identical tool names, your agent calls a handful of domain tools with an action field:

application({ action: "deploy", uuid: "<app-uuid>", wait: true })
diagnose({ action: "scan" })
emergency({ action: "stop_all", confirm: true })

Under the hood, every call goes through the same request pipeline: Zod-validated input, retrying HTTP client, secret-aware output masking, and structured error envelopes with recovery hints — so your agent fails gracefully instead of guessing.

[!NOTE] This is a community project built for people who run their own Coolify instances. It is not affiliated with or endorsed by Coolify Labs.

🆚 Why awesome-coolify-mcp

Typical setup without it	With awesome-coolify-mcp
Several overlapping community MCP tools, each with its own schema	One server, one consistent schema
Dozens of granular, single-purpose tools per resource	10 domain tools × `action` discriminators (32 actions total)
Ad-hoc error strings that agents have to guess at	Structured codes (`COOLIFY_401`, `COOLIFY_404`, …) + machine-readable recovery hints
Secrets can leak straight into agent context	Default secret masking + confirmation gates on destructive actions
Read a wall of raw JSON to find what changed	Bounded, paginated projections tuned for LLM context windows

Today, the focus is squarely on day-2 operations: verifying connectivity, discovering what you have, deploying and watching it roll out, pulling logs, diagnosing unhealthy apps and servers, scanning the whole fleet for issues, and running gated emergency actions when something is on fire. Creating brand-new applications, services, and databases from a blank slate is on the way — see Coming soon.

✨ Features

Action-based tools across 10 domains — call application({ action: "deploy", uuid }) instead of hunting through dozens of tool names. Every domain (system, resource, diagnose, application, deployment, service, database, emergency, docs, meta) follows the same shape.
Ops workflows that mirror real incidents — a single system.infrastructure_overview call for the big picture, fuzzy resource.find when you only remember a name or domain, diagnose.app / diagnose.server for a specific suspect, and diagnose.scan when you just know something is wrong fleet-wide.
Deploy lifecycle that agents can actually drive — start/stop/restart, deploy with optional wait-and-poll or force rebuild, list/get/cancel deployments, and bounded runtime or build logs that won't blow your context window.
Service & database lifecycle — start/stop/restart/get, plus service redeploy with an optional fresh image pull.
Safety by default, not by convention — emergency mutations require an explicit confirm: true; sensitive keys (password, token, secret, private, env) render as *** unless you opt in with reveal: true.
Agent-friendly failure modes — every error is a parseable envelope with a code, a human message, and recoveryHints; transient network/429/5xx failures retry automatically with exponential backoff.
Broad client coverage out of the box — Cursor, VS Code / GitHub Copilot, Claude Desktop, Claude Code, Windsurf, and 15+ more via the install configurator.

🏗️ How it works

MCP client (Cursor / Claude / VS Code / …)
        │  stdio MCP
        ▼
awesome-coolify-mcp  (10 domain tools + action discriminator)
        │  HTTPS + Bearer token
        ▼
Coolify REST API 4.1.x  (servers · projects · applications · services · databases)

The server itself is intentionally boring: it holds no long-lived state and never touches your IDE's config files. Your MCP host (Cursor, Claude, VS Code, …) injects COOLIFY_URL and COOLIFY_TOKEN through its MCP config's env block; the process reads them from its environment (or an optional local .env when you run it directly from the CLI) and forwards authenticated requests to your Coolify instance over HTTPS.

🚀 Quick start

Prerequisites

Node.js 20+
A self-hosted Coolify instance on 4.1.x
An API token from Coolify → Keys & Tokens (authorization docs)

Run it directly with npx — no global install needed:

npx -y awesome-coolify-mcp

Wire the two required environment variables into your MCP host (see Install for every client). Once connected, a minimal smoke test looks like this:

meta({ action: "version" })                       // server identity — no Coolify call
system({ action: "verify" })                      // authenticate + connectivity check
system({ action: "infrastructure_overview" })     // servers, projects, apps, services, DBs at a glance

[!IMPORTANT] Emergency actions (stop_all, redeploy_project, restart_project) require confirm: true. Call them without confirm first — you'll get a would_affect preview and no mutation runs. Only pass reveal: true when you genuinely need plaintext secrets back.

📦 Install

There are three equally supported paths — pick whichever fits your workflow.

1. One-click deeplink

Best when you already have your Coolify URL and token handy. Placeholder credentials work fine too — you'll be prompted to fill them in, or you can swap them afterwards.

<details> <summary>How these links work (click to expand)</summary>

Both editors implement a protocol handler that reads a JSON server configuration straight out of the URL:

Client	Scheme	Encoding
Cursor	`cursor://anysphere.cursor-deeplink/mcp/install?name=…&config=…` (mirrored at `https://cursor.com/en/install-mcp?…` for a friendlier landing page)	`config` is base64-encoded JSON
VS Code / Copilot	`vscode:mcp/install?name=…&config=…`	`config` is URL-encoded JSON

Clicking the button opens your editor, shows the server it's about to add, and lets you review or edit the command/env before accepting — nothing is installed silently. </details>

2. Install configurator (GitHub Pages)

Use the browser configurator to type in your real COOLIFY_URL / COOLIFY_TOKEN and generate a ready-to-paste snippet for your exact client — JSON, TOML, or YAML depending on what that client expects.

Everything runs client-side in your browser. Your token is never sent to a backend, logged, or stored anywhere but the config file you paste it into.

3. Manual MCP config

Paste this into your host's MCP configuration file. Cursor example (~/.cursor/mcp.json for global, or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "awesome-coolify-mcp": {
      "command": "npx",
      "args": ["-y", "awesome-coolify-mcp"],
      "env": {
        "COOLIFY_URL": "https://coolify.example.com",
        "COOLIFY_TOKEN": "YOUR_COOLIFY_API_TOKEN",
        "COOLIFY_VERIFY_SSL": "true",
        "COOLIFY_MCP_LOG": "info"
      }
    }
  }
}

A ready-made copy-paste template also lives at docs/mcp.example.json.

🖥️ Supported clients

Client	Config location	Notes
Cursor	`~/.cursor/mcp.json`	One-click deeplink or manual JSON
VS Code / GitHub Copilot	`.vscode/mcp.json`	Native `inputs` prompts for URL/token — no plaintext in the file
Claude Desktop	`claude_desktop_config.json`	Manual JSON or configurator output today
Claude Code	`~/.claude.json` or `.mcp.json`	stdio via `npx -y awesome-coolify-mcp`
Windsurf	`~/.codeium/windsurf/mcp_config.json`	Same `npx` + `env` pattern as Cursor

The install configurator covers a much wider matrix — OpenCode, Codex CLI, Gemini CLI, Cline, Kilo Code, Goose, LM Studio, Hermes Agent, Kimi Code, Google Antigravity, OpenClaw, and more — with the correct config shape for each.

[!NOTE] Claude Desktop currently ships as manual JSON / configurator output only — a dedicated .mcpb bundle is on the roadmap (see Coming soon).

🔐 Environment variables

Variable	Required	Default	Description
`COOLIFY_URL`	yes	—	Coolify base URL, no trailing slash — e.g. `https://coolify.example.com`
`COOLIFY_TOKEN`	yes	—	Bearer API token, scoped to your team
`COOLIFY_VERIFY_SSL`	no	`true`	Set to `false` only for self-signed certs on local/dev instances
`COOLIFY_MCP_LOG`	no	`info`	Log verbosity: `debug` · `info` · `error`

Credentials are read from the process environment (your IDE's MCP env block) or an optional local .env file when running the CLI directly. They are never echoed back inside tool responses.

🧰 Tools reference

Every domain is exposed as one MCP tool with an action discriminator, so your agent's tool list stays short while the capability surface stays wide.

system({ action: "health" })
application({ action: "deploy", uuid: "<app-uuid>", wait: true })
emergency({ action: "stop_all", confirm: true })

🖥️ `system` — connectivity & overview

Your first call in any session: is Coolify reachable, and what does the fleet look like right now?

Action	Purpose
`health`	Verify Coolify API reachability
`version`	Coolify instance version string
`verify`	Authenticate; returns connectivity + version in one call
`infrastructure_overview`	Aggregate counts across servers, projects, applications, services, databases

🏷️ `meta` — server identity

Action	Purpose
`version`	awesome-coolify-mcp's own package name + semver — no Coolify call at all

🔎 `resource` — discovery

For when you know roughly what you're looking for but not its exact UUID.

Action	Purpose
`list`	Applications, services, and databases as summary projections, with pagination `_meta`
`find`	Fuzzy search by name, domain, or IP across servers and resources — ranked, capped at 10

🩺 `diagnose` — investigation

The tool you reach for when something feels wrong but you don't yet know what.

Action	Purpose
`app`	App status, health, env var count, and recent deployments
`server`	Server resources, domains, and reachability
`scan`	Fleet-wide issues grouped by severity — the "what's on fire" button

🚀 `application` — app operations

Action	Purpose
`get`	Detailed application configuration
`start` / `stop` / `restart`	Container lifecycle control
`deploy`	Trigger a deploy, with optional `wait`/poll and `force` rebuild
`logs`	Paginated runtime or build logs, bounded so they never blow your context

📈 `deployment` — deploy tracking

Action	Purpose
`list`	Deployments for a given application
`get`	Status, commit, and timing details for one deployment
`cancel`	Cancel an in-flight deployment cleanly

🧩 `service` / `database` — sidecar lifecycle

Tool	Actions
`service`	`get`, `start`, `stop`, `restart`, `deploy` (with optional fresh image pull)
`database`	`get`, `start`, `stop`, `restart`

📚 `docs` — offline guides

Action	Purpose
`search`	Search a bundled, curated Coolify troubleshooting index — not a live web fetch, so it works offline and can't be used as an external fetch vector

🚨 `emergency` — high-impact ops (gated)

Reach for these only when you mean it — every action below is behind a confirmation gate.

Action	Purpose
`stop_all`	Stop every running application, fleet-wide — requires `confirm: true`
`redeploy_project`	Redeploy every app in a project — requires `confirm: true`
`restart_project`	Restart every app in a project — requires `confirm: true`

🛡️ Safety model

Confirmation gate

Destructive emergency actions follow a strict two-step pattern:

Call with confirm omitted or false → you get back a would_affect preview and error code COOLIFY_CONFIRM_REQUIRED — nothing is mutated.
Call again with confirm: true → the action actually executes.

Regular app/service/database mutations (start, stop, deploy, …) are not behind this gate — they simply follow Coolify's own API semantics, since they're scoped to one resource rather than your whole fleet.

Secret masking

Keys matching password, token, secret, private, or env render as *** by default in tool output.
Pass reveal: true only when you explicitly need plaintext — for example, to copy an env var into another system.
Log line bodies are not masked. Treat raw logs like you would any other sensitive output: don't paste them into long-lived agent memory or public tickets.

⚠️ Structured errors & retries

Every API failure comes back as a parseable envelope your agent can reason about, instead of a raw stack trace:

{
  "code": "COOLIFY_401",
  "message": "Unauthorized — invalid or expired API token",
  "recoveryHints": [
    "Verify the token in Coolify UI → Keys & Tokens",
    "Ensure the token has the required team permissions"
  ],
  "httpStatus": 401
}

Code	Meaning
`COOLIFY_401`	Invalid or missing token
`COOLIFY_404`	Resource not found
`COOLIFY_422`	Validation error
`COOLIFY_500`	Coolify server error
`COOLIFY_NETWORK`	Connection failed
`COOLIFY_TIMEOUT`	Request timed out
`COOLIFY_CONFIRM_REQUIRED`	Emergency preview — pass `confirm: true` to proceed
`COOLIFY_AMBIGUOUS_MATCH`	Name matched multiple resources — pick a UUID from the ranked list

Transient failures (HTTP 429, 5xx, or network errors) retry automatically up to 3 times with exponential backoff (1s → 2s → 4s) before giving up and returning the error to your agent.

💬 Example agent workflows

"Is my Coolify reachable, and what do I have?"

system({ action: "verify" })
system({ action: "infrastructure_overview" })
resource({ action: "list" })

"Find the nginx app, deploy it, then show me the logs."

resource({ action: "find", query: "nginx" })
application({ action: "deploy", uuid: "<uuid>", wait: true })
application({ action: "logs", uuid: "<uuid>" })

"Something feels wrong across the fleet."

diagnose({ action: "scan" })
diagnose({ action: "app", uuid: "<suspect>" })
diagnose({ action: "server", uuid: "<server>" })

"Emergency: stop everything, but let me see the blast radius first."

emergency({ action: "stop_all" })                 // preview — would_affect, no mutation
emergency({ action: "stop_all", confirm: true })  // execute

✅ Status today

The server is stable and actively used for day-2 operations against real Coolify 4.1.x instances:

Capability	Status
Verify connectivity + infrastructure overview	✅ Shipped
Discovery: `resource.list` / `resource.find`	✅ Shipped
Diagnose: app, server, fleet-wide scan + follow-up hints	✅ Shipped
Deploy lifecycle: start/stop/restart, deploy with wait-mode + force rebuild	✅ Shipped
Deployment tracking: list / get / cancel	✅ Shipped
App logs: runtime + build, bounded and paginated	✅ Shipped
Service & database lifecycle	✅ Shipped
Emergency ops: stop-all, project redeploy/restart, behind confirm gate	✅ Shipped
Secret masking with explicit `reveal` opt-in	✅ Shipped
Structured errors, recovery hints, automatic retries	✅ Shipped
npm distribution + install configurator for 15+ clients	✅ Shipped

Service/database log tailing is temporarily on hold — Coolify 4.1.x's REST API doesn't expose a /services/{uuid}/logs or /databases/{uuid}/logs endpoint yet (the fix has merged upstream but isn't backported to 4.1.x). It'll ship the moment the endpoint is reachable, with no half-working stub in the meantime.

🔮 Coming soon

The next milestone focuses on creation, not just operation — turning awesome-coolify-mcp into a tool that can stand up new infrastructure from scratch, not only manage what already exists. Planned areas, roughly in order of priority:

Full CRUD for applications, services, databases, and servers — create, update, and delete, not just start/stop/deploy
Environment variable management — read, write, bulk-sync from a local .env
One-click services — full service catalog with compose YAML, storage, and env configuration
Database backups — schedules, executions, and on-demand triggers
Scheduled tasks — cron job CRUD, execution history, run-once triggers
Teams & multi-tenancy — list/get teams and members, per-project scoped tokens
Private keys & cloud providers — SSH key management, Hetzner/DigitalOcean provisioning tokens
GitHub App integration — repo/branch discovery, enterprise URLs
Claude Desktop .mcpb packaging — true one-click install, no manual JSON
Deeper observability — container-level metrics, Traefik insight, live event streams, log search

Have a use case that isn't listed? Open an issue — the roadmap is shaped by what the community actually runs into.

🛠️ Local development

git clone https://github.com/clezcoding/awesome-coolify-mcp.git
cd awesome-coolify-mcp
npm install
npm run build    # tsup → dist/
npm test         # vitest
npm run dev      # watch mode

Logs go to stderr only — stdout is reserved exclusively for the MCP protocol.

The maintainer publish flow (build → pack --dry-run → publish) is documented in CONTRIBUTING.md.

🔗 Links

Resource	URL
Install configurator	clezcoding.github.io/awesome-coolify-mcp/install.html
Install landing page	clezcoding.github.io/awesome-coolify-mcp/
Example MCP JSON	docs/mcp.example.json
Brand assets	docs/assets/
Coolify	coolify.io
MCP specification	modelcontextprotocol.io
Issues & feature requests	GitHub Issues
Contributing	CONTRIBUTING.md
License	MIT

Recommended Servers

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official

Featured

TypeScript

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official

Featured

Local

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official

Featured

TypeScript

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official

Featured

Python

E2B

Using MCP to run code via e2b.

Official

Featured

Neon Database

MCP server for interacting with Neon Management API and databases

Official

Featured

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official

Featured

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official

Featured

awesome-coolify-mcp

README

📋 Table of contents

🔭 Overview

🆚 Why awesome-coolify-mcp

✨ Features

🏗️ How it works

🚀 Quick start

📦 Install

1. One-click deeplink

2. Install configurator (GitHub Pages)

3. Manual MCP config

🖥️ Supported clients

🔐 Environment variables

🧰 Tools reference

🖥️ system — connectivity & overview

🏷️ meta — server identity

🔎 resource — discovery

🩺 diagnose — investigation

🚀 application — app operations

📈 deployment — deploy tracking

🧩 service / database — sidecar lifecycle

📚 docs — offline guides

🚨 emergency — high-impact ops (gated)

🛡️ Safety model

Confirmation gate

Secret masking

⚠️ Structured errors & retries

💬 Example agent workflows

✅ Status today

🔮 Coming soon

🛠️ Local development

🔗 Links

Recommended Servers

🖥️ `system` — connectivity & overview

🏷️ `meta` — server identity

🔎 `resource` — discovery

🩺 `diagnose` — investigation

🚀 `application` — app operations

📈 `deployment` — deploy tracking

🧩 `service` / `database` — sidecar lifecycle

📚 `docs` — offline guides

🚨 `emergency` — high-impact ops (gated)