PlugWiki
Coolify MCP logo

Coolify MCP Server by StuMason: Setup for Claude, Cursor and Other Apps

CommunityLocal
Getnpm@masonator/coolify-mcpstumason/coolify-mcp

Not the official Coolify MCP server. This one is built by the community. Coolify makes its own: Coolify MCP Server →

Lets Claude, Cursor and other assistants diagnose, deploy and manage the apps, databases and servers on your self-hosted Coolify.

This community server connects your assistant to your own Coolify instance with an API token. It can find problems, read logs, deploy, restart and roll back apps, and create or delete projects, databases and services. It runs on your computer by default and talks only to your Coolify. It is not made by Coolify, which has its own built-in server.

Good for

  • Developers who run their own apps on a Coolify server
  • Small teams who want an assistant to explain a failed deploy
  • Agencies and home-lab owners with several Coolify instances

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Coolify MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Coolify MCP server to Claude Code. Run this command:
    
    claude mcp add coolify -e COOLIFY_BASE_URL=<COOLIFY_BASE_URL> -e COOLIFY_ACCESS_TOKEN=<COOLIFY_ACCESS_TOKEN> -- npx -y @masonator/coolify-mcp
    
    Ask me for COOLIFY_BASE_URL, COOLIFY_ACCESS_TOKEN and only put the values in that config, nowhere else.
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js (npx), A running Coolify v4 instance.

Read-only mode: No read-only switch in the local server. Use a token from a view-only user.

Create the token in Coolify under Keys & Tokens, then API tokens. Run the doctor command from the project README to check the setup.

Built from the package data we hold. Not yet tested by us.

Tools

  • Counts everything in your Coolify

    Returns how many servers, projects, applications, databases and services your Coolify has, as a quick map of the estate.

    Try: “Give me an overview of my infrastructure.”

    Read · get_infrastructure_overview

  • Scans your estate for problems

    Looks across all resources for ones that are unhealthy or misconfigured and lists what it found.

    Try: “Find any issues in my infrastructure.”

    Read · find_issues

  • Works out why an app is unhealthy

    Takes an app UUID, name or domain and gathers its status, recent deployments and logs to explain what is wrong.

    Try: “Diagnose my shop.example.com app.”

    Read · diagnose_app

  • Works out why a server is unhealthy

    Takes a server UUID, name or IP and gathers its status and resources to explain what is wrong.

    Try: “Diagnose the server at 10.0.0.5.”

    Read · diagnose_server

  • Lists your applications

    Returns each application as a short summary with its UUID, name and status.

    Try: “List my applications.”

    Read · list_applications

  • Shows one application in full

    Returns the full record for one application. Passwords, webhook secrets and compose bodies come back masked unless the call asks for them.

    Try: “Show me the settings for application abc123.”

    Read · get_application

  • Lists your databases

    Returns each database as a short summary with its UUID, name and status.

    Try: “Which databases do I have running?”

    Read · list_databases

  • Shows one database in full

    Returns the full record for one database. Passwords and connection URLs come back masked unless the call asks for them.

    Try: “Show the details of my Postgres database.”

    Read · get_database

  • Lists your services

    Returns each service (a multi-container stack) as a short summary.

    Try: “List my services.”

    Read · list_services

  • Shows one service in full

    Returns the full record for one service. Compose bodies and secrets come back masked unless the call asks for them.

    Try: “Show the details of my Plausible service.”

    Read · get_service

  • Lists your servers

    Returns the servers Coolify manages, as short summaries.

    Try: “List my servers.”

    Read · list_servers

  • Shows one server in full

    Returns the record for one server. Sentinel and log-drain credentials are always masked.

    Try: “Show details for server localhost.”

    Read · get_server

Read from the source code

Permissions

high risk · 9 things to watch

High risk

With an API token, the assistant can read your logs and settings, and it can deploy, stop and delete apps, databases and servers. Use a token with only the access you need, and use a client that shows the confirm prompt.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can delete apps, databases and keys

    Delete actions cover applications, databases, services, projects, environments, storages, backups, SSH keys, GitHub Apps and cloud tokens. Deleting a resource can remove its volumes too, so read the prompt before you approve. github.com

  • One call can stop or redeploy everything

    Tools can stop all running apps, redeploy or restart a whole project, change one variable across many apps, and switch the Coolify API off. These ask you first, but only on clients that support that prompt. github.com

  • It can run commands on your containers

    The scheduled task tool can run a command once on an app or service and return the output. Treat it as shell access to those containers. github.com

  • It can create servers that cost money

    The Hetzner tool can create a new server with a cloud token stored in Coolify. The source marks it as one that spends real money. github.com

  • No confirm prompt in some apps, no read-only mode

    Confirmations need a client that supports elicitation. Claude Desktop and claude.ai run these calls without that prompt over stdio. A read-only switch exists only in the HTTP mode. github.com

  • It can reveal secrets when asked

    Env var values, database passwords and webhook secrets come back masked, but a call with reveal set returns one exact key in plain text. Your assistant then sees that secret. github.com

  • Your Coolify token sits in the client config

    The API token and Coolify URL are environment variables. Use a token with only the access you need, or point to a token file so you can rotate it. github.com

  • Log text is wrapped as untrusted data

    Logs come back inside a marked boundary so a poisoned log line reads as data. This lowers the risk and does not remove it. github.com

  • It fetches one docs file from coolify.io

    Apart from your Coolify instance, the only outbound request is a documentation index refresh from coolify.io with no credentials. The project states it has no telemetry. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyThe local stdio server has no read-only switch. The HTTP mode has MCP_READONLY=true, which registers only the read tools.
Talks toYour Coolify instance (the URL you set). coolify.io (one docs index refresh)
Sign-in and keysThe Coolify URL and API token sit in your client config as environment variables, or the token can come from a file that the server re-reads.

Questions

Is the Coolify MCP server by StuMason official?

No. It is a community project by Stu Mason, not made by the Coolify team. Coolify has its own built-in server that you turn on in its settings, so check the Coolify built-in MCP server first.

How is it different from the built-in Coolify server?

The built-in server runs inside your Coolify with nothing to install, and needs no third-party code to hold your token. This one runs on your computer or as its own container, works over stdio, adds diagnose and bulk tools and can reach several Coolify instances. The project README calls the built-in one read-only; see the built-in server page for what it can do in current Coolify versions.

What credentials does it need?

Your Coolify URL and an API token from Keys & Tokens in Coolify. A token from a Member-role user can only view resources.

Can it run read-only?

Not in the local install. Only the HTTP mode has a read-only switch. Using a token from a user who can only view is the other way to limit it.

Can it delete my apps and databases?

Yes. It can delete apps, databases, services, projects, SSH keys and more. On clients that support confirm prompts it asks first, and a delete can remove volumes unless you say to keep them.

Does it run on my computer or in the cloud?

On your computer by default, and it talks to your Coolify over the network. It can also run as a container inside your Coolify, and clients then sign in with OAuth.

Can it see my passwords and secrets?

Values come back masked. A call can ask for one exact variable in plain text, and then the assistant sees it. A Coolify token without sensitive-read access cannot get plaintext at all.

Why did it ask me to confirm?

Delete and bulk actions pause and ask you in your own client, naming how much will be affected. Clients without that support skip the prompt.

Is it free?

Yes. It is MIT licensed, and the license file ships in the npm package.

Information

updated Nov 2, 2026

Publisher
Community
Package
@masonator/coolify-mcp
Registry
npm
Transport
stdio
Auth
token in env
License
MIT
Last commit
Oct 27, 2026
Open issues
8

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Other Coolify MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 7
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com
  4. github.com · github.com
  5. github.com · github.com
  6. github.com · github.com
  7. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.