We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Coolify MCP

MCP server by Stuart Mason

Deploy, diagnose and operate a self-hosted Coolify PaaS from your AI assistant, with human confirmation for destructive actions.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install Coolify MCP

Runs on your machine. Your client starts it with this command:

npx -y @masonator/coolify-mcp

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

  • COOLIFY_ACCESS_TOKEN secret Your Coolify API access token
  • COOLIFY_BASE_URL optional Your Coolify instance URL

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/coolify

About

Connects to a Coolify v4 instance and lets an assistant deploy applications, read container logs, diagnose apps and servers, manage databases, services, projects, environment variables, backups and scheduled tasks, and search the Coolify docs. Destructive operations ask the user to confirm first, and secrets are masked in responses.

Runs locally over stdio with npx @masonator/coolify-mcp, or as a one-click MCPB bundle for Claude Desktop. It can also be deployed as a container next to Coolify for remote use. Needs a Coolify API token in COOLIFY_ACCESS_TOKEN and optionally the instance URL in COOLIFY_BASE_URL.

What you can do

  • Diagnose apps and servers by name, domain, IP or UUID
  • Scan the estate for issues and read container logs
  • Deploy applications and roll back, waiting for a final status
  • Start, stop and restart resources
  • Create and manage applications, databases, services and projects
  • Manage env vars, storages, backups and scheduled tasks with masked secrets
  • Run bulk operations behind human confirmation
  • Search the Coolify documentation

Tools

Local servers list their tools once they’re running, so we can’t show them here. Look for the list in its documentation; your client shows them after you add it.

Example prompts

  • Why is my app at example.com failing? Diagnose it.

  • Deploy the staging application and show the log tail if it fails.

  • Scan my Coolify estate for unhealthy resources.

  • Search the Coolify docs for how to configure persistent storage.

Set up

Every client starts Coolify MCP on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio coolify --env "COOLIFY_ACCESS_TOKEN=<YOUR_COOLIFY_ACCESS_TOKEN>" -- npx -y @masonator/coolify-mcp
  1. Start Claude Code and type /mcp. coolify should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_ACCESS_TOKEN": "<YOUR_COOLIFY_ACCESS_TOKEN>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_ACCESS_TOKEN": "<YOUR_COOLIFY_ACCESS_TOKEN>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "coolify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_ACCESS_TOKEN": "${input:coolify-access-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "coolify-access-token",
      "description": "COOLIFY_ACCESS_TOKEN",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_ACCESS_TOKEN": "<YOUR_COOLIFY_ACCESS_TOKEN>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add coolify --env "COOLIFY_ACCESS_TOKEN=<YOUR_COOLIFY_ACCESS_TOKEN>" -- npx -y @masonator/coolify-mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.coolify]
command = "npx"
args = ["-y", "@masonator/coolify-mcp"]
env = { COOLIFY_ACCESS_TOKEN = "<YOUR_COOLIFY_ACCESS_TOKEN>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "COOLIFY_ACCESS_TOKEN=<YOUR_COOLIFY_ACCESS_TOKEN>" coolify npx -- -y @masonator/coolify-mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "@masonator/coolify-mcp"
      ],
      "env": {
        "COOLIFY_ACCESS_TOKEN": "<YOUR_COOLIFY_ACCESS_TOKEN>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

Embed

Show Coolify MCP in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Coolify MCP on mcp.tc](https://mcp.tc/i/coolify/badge.svg)](https://mcp.tc/i/coolify)
HTML
<a href="https://mcp.tc/i/coolify"><img src="https://mcp.tc/i/coolify/badge.svg" alt="Coolify MCP on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/coolify.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/coolify" title="Coolify MCP on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/coolify.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Coolify MCP card to your site.

Markdown
Add the mcp.tc card for Coolify MCP, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/coolify.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="coolify"><a href="https://mcp.tc/i/coolify">Coolify MCP on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Coolify MCP on mcp.tc](https://mcp.tc/i/coolify/badge.svg)](https://mcp.tc/i/coolify)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow Coolify MCP and we’ll email you when something changes.

  1. , Automatic check

    New version 3.10.1 (was 3.9.0). Read from npm.

  2. , Automatic check

    Tracking started: version 3.9.0.

FAQ

Can I paste mcp.tc/i/coolify into my MCP client?

No. Coolify MCP runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @masonator/coolify-mcp.

Does Coolify MCP need an API key?

Yes. It reads COOLIFY_ACCESS_TOKEN from its environment, and COOLIFY_ACCESS_TOKEN is a secret. Put the value in your client’s config on your own machine, never in a shared file.

Is Coolify MCP a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @masonator/coolify-mcp, which needs Node.js.

What can Coolify MCP do?

You can diagnose apps and servers by name, domain, IP or UUID, scan the estate for issues and read container logs and deploy applications and roll back, waiting for a final status.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to Coolify MCP?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Coolify MCP’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Stuart Mason. This page was built from Coolify MCP’s public metadata, last checked on 12 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.