Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Coolify MCP Server

MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search.

by Stuart Mason·added 2026-06-06·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions.
  • Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once.
  • Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation.
  • Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually.
  • Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure.

Privacy notes

  • Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client.
  • Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors.
  • Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials.
  • Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance.
  • Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs.

Prerequisites

  • Running Coolify instance with API access enabled.
  • Coolify API access token scoped to the resources Claude may inspect or manage.
  • Node.js 20 or newer for the published npm server.
  • Review of which servers, projects, applications, databases, services, deployments, env vars, private keys, teams, cloud tokens, and scheduled tasks the token can access.
  • Optional auth-proxy headers only when required by trusted Cloudflare Access or similar middleware.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Community-maintained MIT MCP server for Coolify. Coolify is a separate self-hosted PaaS; users must follow their infrastructure, team, cloud provider, repository, and deployment policies.
Full copyable content
{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": ["-y", "@masonator/coolify-mcp"],
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.example",
        "COOLIFY_ACCESS_TOKEN": "your-api-token"
      }
    }
  }
}

About this resource

Content

Coolify MCP Server connects Claude and other MCP clients to Coolify through the Coolify API. It exposes optimized tools for infrastructure overview, diagnostics, servers, projects, environments, applications, databases, services, deployments, logs, env vars, storage, scheduled tasks, private keys, GitHub apps, teams, cloud tokens, Hetzner helpers, and Coolify documentation search.

Use it when Claude needs supervised access to inspect, troubleshoot, deploy, or manage self-hosted Coolify infrastructure.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, package metadata, server manifest, quickstart, security guide, server entrypoint, and MCP server implementation for current setup and behavior details.

Features

  • Get infrastructure overviews across servers, projects, applications, databases, and services.
  • Diagnose applications and servers by UUID, name, domain, IP address, or infrastructure state.
  • List and manage Coolify servers, projects, environments, applications, databases, services, deployments, logs, env vars, storages, backups, and scheduled tasks.
  • Start, stop, restart, redeploy, cancel, and inspect resources through consolidated action tools.
  • Manage private keys, GitHub apps, team information, cloud tokens, and Hetzner provisioning helpers when the API token permits it.
  • Search bundled Coolify documentation for troubleshooting and setup guidance.
  • Return compact, token-optimized summaries with suggested next actions and pagination.

Installation

Create a Coolify API token, then configure the stdio server:

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": ["-y", "@masonator/coolify-mcp"],
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.example",
        "COOLIFY_ACCESS_TOKEN": "your-api-token"
      }
    }
  }
}

For Claude Code, the project recommends the package tag form:

claude mcp add coolify -e COOLIFY_BASE_URL=https://your-coolify-instance.example -e COOLIFY_ACCESS_TOKEN=your-token -- npx @masonator/coolify-mcp@latest

Use custom --header flags only for trusted authentication proxies and never store proxy secrets in shared project files.

Use Cases

  • Ask Claude for a compact overview of running Coolify infrastructure.
  • Diagnose a failing app by name, domain, or UUID.
  • Inspect deployment logs before deciding whether to redeploy or roll back.
  • Update environment variables after review.
  • Restart a staging project or redeploy approved applications.
  • Search Coolify docs for health checks, Docker Compose, bad gateway errors, or deployment configuration.

Safety and Privacy

Coolify MCP Server can operate production infrastructure. Keep API tokens least-privileged, start in staging, and require explicit confirmation for starts, stops, restarts, deployments, deletions, batch operations, env-var changes, private-key changes, cloud-token changes, backup actions, and GitHub app changes.

Treat Coolify tokens, auth-proxy headers, server IPs, domains, UUIDs, logs, deployment output, env vars, private keys, cloud-provider tokens, team data, database metadata, and service configuration as sensitive infrastructure data. Avoid sharing MCP transcripts that include logs or secrets.

#coolify#devops#infrastructure#deployments#self-hosted

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.