PlugWiki

Coolify MCP, the server built into Coolify

OfficialRemote

Lets your AI assistant check, deploy and manage the apps, databases and servers in your Coolify, using your own API token.

This is the MCP server built into Coolify itself, so there is nothing to install. It lets Claude Code, Cursor and other assistants look at your servers, apps and databases, read logs, deploy, restart and roll back, and on recent versions create or delete resources. What it can do depends entirely on the API token you give it, so a token with only read access keeps it hands-off. On a self-hosted Coolify you must switch it on first; on Coolify Cloud it is already on.

Good for

  • Self-hosters who want Claude to explain why an app is down or a deploy failed
  • Developers who deploy, restart or roll back apps from Claude Code or Cursor
  • Teams on Coolify Cloud who want a connection with nothing to install
  • Admins who want a read-only view of every project, server and database in one chat

Works in

2 supported · 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 --transport http coolify https://app.coolify.io/mcp \
      --header "Authorization: Bearer <COOLIFY_API_TOKEN>"
    
    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 Coolify API token, MCP enabled on the instance.

Read-only mode: Create the API token with only the read permission. The assistant then gets read tools only and cannot deploy, change or delete anything.

On self-hosted Coolify, first turn on Settings > Advanced > API and MCP > MCP server, and replace app.coolify.io with your own Coolify domain (it must be public HTTPS). Create the token under Keys & Tokens > API Tokens while the right team is active; it is shown once and reaches only that team. Start with the read permission; add deploy to let it deploy, start, stop and roll back, and write to let it create, change and delete. Do not use a root token. Then ask Claude to show your current Coolify team to check it reached the right one.

From the vendor's docs. Source.

Tools

  • Gives a quick overview of your team's servers, resources and their health

    Returns counts of your servers and resources, health hints and open deployments for the team the token belongs to.

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

    Read · get_infrastructure_overview

  • Finds a project, server, app or database by name or domain

    Searches projects, servers and resources by name, ID or domain when you do not know what kind of thing it is.

    Try: “Find whatever is serving blog.example.com”

    Read · search_resources

  • Lists apps, databases and services that look unhealthy or down

    Finds resources that appear unhealthy or stopped, so you can see what needs attention first.

    Try: “What is down in Coolify right now?”

    Read · list_unhealthy_resources

  • Lists your apps, filtered by project, server, status or name

    Returns your applications, with optional filters such as project, environment, server, tag or status.

    Try: “List all apps in the production environment”

    Read · list_applications

  • Shows the details of one app

    Returns the settings and status of a single application. Sensitive values stay hidden unless the token allows them.

    Try: “Show me the details of my api app”

    Read · get_application

  • Reads recent logs from an app, database or service

    Fetches the latest log lines from a running container, 100 by default and up to 500. Needs a token with sensitive-read access.

    Try: “Show the last 200 log lines for my api app”

    Read · get_logs

  • Lists queued, running and past deployments

    Shows deployments that are waiting, running or finished, including an app's deployment history.

    Try: “Show the last five deployments of my web app”

    Read · list_deployments

  • Shows one deployment, with an optional short log summary

    Returns the details of one deployment. With sensitive-read access it can include a short, redacted log summary.

    Try: “Why did deployment abc123 fail?”

    Read · get_deployment

  • Lists your servers and whether they are reachable

    Returns the servers your team can see, optionally only the reachable or unreachable ones.

    Try: “Which of my servers are unreachable?”

    Read · list_servers

  • Shows the details of one server

    Returns one server's details. Connection secrets stay hidden.

    Try: “Show details for my hetzner-1 server”

    Read · get_server

  • Shows a server's CPU, memory, disk and network use over time

    Returns monitoring numbers for a server over a time range you choose, if metrics are turned on for that server.

    Try: “How has CPU on hetzner-1 looked over the last day?”

    Read · get_server_metrics

  • Lists the domains hosted on a server

    Returns every domain served from one server.

    Try: “Which domains run on hetzner-1?”

    Read · get_server_domains

From the official docs

Pros and cons

Good

  • Built into Coolify by its own team, so there is nothing to install or keep updated.
  • The token's permissions decide which tools even appear, so a read token is truly read-only.
  • Covers servers, projects, apps, databases, services, deployments, logs, backups and scheduled tasks.
  • Secrets such as private keys, passwords and webhook URLs are never sent to the assistant.
  • Actions made through it show in the team audit log.
  • Comes with guided prompts for troubleshooting an app and explaining a failed deploy.

Watch out

  • Off by default on self-hosted Coolify, and your instance needs a public HTTPS address.
  • Creating, changing and deleting resources needs Coolify 4.5.0 or later; 4.1 and 4.2 can only read, and 4.3 and 4.4 add deployment controls.
  • One token reaches only one team, so several teams mean several connections.
  • No sign-in with your Coolify account; you paste an API token.
  • Log redaction is best effort, so sensitive logs can still reach the assistant.
  • Only Claude Code and Cursor have setup guides from Coolify.

Permissions

high risk · 5 things to watch

High risk

With a write or deploy token, the assistant can stop, delete or roll back your apps and databases, and even buy a server at your cloud provider. Start with a read-only token for one team, and add deploy or write only when you need them.

What it can do

Watch out for

  • A write token can delete apps and databases

    With write, the assistant can delete applications, databases and services; with deploy, it can stop containers and roll back. Use a read-only token unless you need changes. coolify.io

  • It can create a paid server at your provider

    If you saved a cloud provider token in Coolify, a write token can provision a new server that you pay for. Keep your client set to ask before risky actions. coolify.io

  • Logs can still contain secrets

    Coolify says log redaction is best effort. Only add the sensitive-read permission when the assistant must read logs or environment values. coolify.io

  • Never give it a root token

    Coolify says not to use root tokens for normal MCP access. A regular token reaches only one team. coolify.io

  • Risky actions need a confirmation

    Deletes, stops and rollbacks only run when the assistant sends an explicit confirmation, which your client should ask you for first. coolify.io

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyCreate the API token with only the read permission. MCP then lists only read tools; deploy and write tools do not appear.
Sign-in and keysCoolify API token sent as a Bearer header and saved in your client's config. The full token is shown once when created.
Data retentionResponses never include private keys, S3 secrets, tokens, passwords or webhook URLs. Log summaries are capped and redacted on a best-effort basis.
Scopes
  • read

  • read:sensitive

  • deploy

  • write

Alternatives

Use the built-in server if you want nothing to install; it needs Coolify 4.5 or later to create or change resources. StuMason's coolify-mcp is the pick on older versions or when you want its diagnose and bulk tools.

ServerOfficialRunsSign-inCan change thingsToolsGitHub stars
For Coolify
Coolify MCP ServerThis pageOfficialHostedAPI tokenYes77–
coolify-mcpCommunityLocalAPI tokenYes46617
Other tools for the same job
coolify-mcp-server (kof70)CommunityLocal–––28

Questions

Is the Coolify MCP server free?

Yes. It is part of Coolify, so it costs nothing extra on self-hosted Coolify and is included on Coolify Cloud.

What is the Coolify MCP server URL?

On Coolify Cloud it is https://app.coolify.io/mcp. On a self-hosted instance it is your Coolify address followed by /mcp, for example https://coolify.example.com/mcp.

How do I turn it on?

On self-hosted Coolify, open Settings > Advanced and set MCP server to Enabled in the API and MCP section. On Coolify Cloud it is already on.

Why does the address return 404 or 403?

A 404 means MCP is off for the whole instance. A 403 means a team admin turned it off for your team. On self-hosted Coolify, the Allowed IPs list also applies.

Is it read-only?

Only if you make it so. Give it a token with just the read permission and the change tools never appear. Since Coolify 4.5.0, a token with write access can create, change and delete resources.

Which Coolify version do I need?

4.1.0 or later. MCP first shipped in 4.1.0 with read-only tools, deployment controls arrived in 4.3.0, and tools to create, change and delete resources in 4.5.0.

Can it delete my apps or databases?

Yes, with a token that has the write permission. Each delete needs an explicit confirmation, so set your assistant to ask you before it runs risky actions.

Can one connection reach all my teams?

No. Each token belongs to one team, and the assistant only sees that team's resources. Add one connection per team.

Built-in server or StuMason's coolify-mcp?

Use the built-in one if you want nothing to install; it needs Coolify 4.5 or later to create or change resources. StuMason's community server runs on your computer, works with older versions and adds diagnose and bulk actions.

Examples

  • Check the connection reaches the right team

    Show my current Coolify team and an overview of its infrastructure.

  • Find what is down

    Which of my Coolify resources look unhealthy right now?

  • Explain why a deployment failed, using Coolify's built-in guided prompt

    Explain why the last deploy of my api app failed.

  • Troubleshoot an application with optional live logs

    My blog app returns 502. Troubleshoot it and check the logs.

Information

updated Nov 1, 2026

Publisher
Official
Transport
Streamable HTTP
Auth
API key
Last commit
Nov 2, 2026

DocsChangelog

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 17
  1. Set up MCP · coolify.io
  2. Connect other MCP clients · coolify.io
  3. What is MCP? · coolify.io
  4. MCP overview · coolify.io
  5. MCP capabilities · coolify.io
  6. MCP security · coolify.io
  7. Servers · coolify.io
  8. Logs · coolify.io
  9. How MCP works · coolify.io
  10. Coolify v4.1.0 release notes · github.com
  11. Coolify v4.3.0 release notes · github.com
  12. Coolify v4.5.0 release notes · github.com
  13. stumason/coolify-mcp · github.com
  14. Claude Code · coolify.io
  15. Cursor · coolify.io
  16. Prompts and resources · coolify.io
  17. Coolify v4.4.0 release notes · github.com

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