coolify-mcp MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

38 tools across servers, applications, databases (8 engines), services, teams
Batch ops: restart all apps in a project, bulk env updates, emergency stop
Full-text search over Coolify docs built in — no tab-switching
Responses 90-99% smaller than raw Coolify API — survives long conversations
Works with Claude Desktop, Claude Code, Cursor

라이브 데모

실제 사용 모습

coolify.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "coolify-mcp"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "coolify-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "coolify-mcp"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": [
        "-y",
        "coolify-mcp"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "coolify",
      "command": "npx",
      "args": [
        "-y",
        "coolify-mcp"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "coolify": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "coolify-mcp"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add coolify -- npx -y coolify-mcp

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: coolify-mcp

Deploy a new app to Coolify from a Git URL by chat

👤 Solo devs, indie hackers self-hosting ⏱ ~10 min beginner

언제 쓸까: You have a new side project on GitHub and want it live on your VPS in under 5 minutes without clicking through Coolify's UI.

사전 조건

Running Coolify instance — coolify.io install script on your VPS
COOLIFY_ACCESS_TOKEN — Coolify > Settings > API > Create Token

흐름

Create the app

Create a new Coolify app in project 'side-projects' on server 'hetzner-fsn1'. Source: https://github.com/me/my-app. Build pack: Nixpacks. Port: 3000.✓ 복사됨

→ App created with a UUID returned
Set env vars

Set these env vars on the app: DATABASE_URL=..., SESSION_SECRET=..., NODE_ENV=production.✓ 복사됨

→ Env vars saved
Deploy and watch logs

Deploy the app. Tail the build log; tell me when it's healthy or if it crashes.✓ 복사됨

→ Live build log + final success/fail verdict

결과: A new HTTPS app running on your VPS in ~5 minutes, all from chat.

함정

Forgot to set a domain; Coolify uses an ugly auto-generated one — After deploy, ask: 'Add custom domain app.example.com with HTTPS'. Coolify auto-provisions Let's Encrypt.

함께 쓰기: github

Spin up a managed Postgres for your new app in one prompt

👤 Full-stack devs ⏱ ~5 min beginner

언제 쓸까: Your app needs a DB and you don't want to shell in, docker run, and remember backup cron.

흐름

Create the database

Create a Postgres 16 database named 'myapp-prod' in project 'side-projects' with 2GB RAM, daily backups retained 7 days.✓ 복사됨

→ Database created, credentials returned
Connect it to your app

Add the DATABASE_URL for this DB as an env var on app 'my-app', and redeploy.✓ 복사됨

→ Env var set + redeploy triggered

결과: Managed Postgres with scheduled backups, wired into your app.

함정

Default Postgres accepts connections only from Coolify network — Set Public toggle via the MCP if you need external access — and open only specific IPs

함께 쓰기: postgres

Diagnose and recover from a production app crash from your phone

👤 Solo ops, small teams ⏱ ~10 min intermediate

언제 쓸까: Your app is down and you're away from your desk. You have Claude on your phone and your Coolify token.

흐름

Check health

Show me the status of all apps in project 'prod'. Anything unhealthy?✓ 복사됨

→ Per-app status list with reds flagged
Look at logs

Tail the last 200 lines of app 'api-server'. What's the error?✓ 복사됨

→ Log excerpt + probable cause
Roll back or restart

Restart the app. If it crashes again within 2 minutes, redeploy the previous commit.✓ 복사됨

→ Restart issued; state monitored

결과: Recovered service without needing a laptop.

함정

Restart won't fix a bad deploy — you'll just loop — Tell Claude to look at deploy history and roll back to the last healthy commit if restart doesn't help

함께 쓰기: sentry

Rotate a shared secret across every app in a project

👤 Small DevOps teams ⏱ ~10 min intermediate

언제 쓸까: You rotated an API key (Stripe, Sentry DSN, etc.) and 6 apps all reference it.

흐름

List affected apps

In project 'prod', list all apps that have the env var 'STRIPE_SECRET_KEY'.✓ 복사됨

→ List of matching apps
Bulk update and redeploy

Update STRIPE_SECRET_KEY to [new value] on all those apps, then trigger redeploy for each with a 30-second stagger.✓ 복사됨

→ Per-app update + redeploy report

결과: Fleet-wide secret rotation in one conversation.

함정

Staggered redeploy still causes brief downtime — If zero-downtime required, use Coolify's rolling deploy mode per app

조합

다른 MCP와 조합해 10배 효율

coolify + github

When a new repo is ready, deploy it to Coolify and comment the URL back on the PR

Take repo me/new-project. Deploy it to Coolify under project 'preview', then comment the preview URL on the main branch README.✓ 복사됨

coolify + sentry

When Sentry shows a spike on a Coolify-hosted app, redeploy the previous version

If Sentry issue count for app 'api-server' doubles in 10 min, roll back the Coolify deploy to previous commit.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
list_servers		Discover attached servers before creating resources	1 API call
list_applications	project_uuid?: str	Find existing apps; scope to a project for less noise	1 API call
create_application	source, server, project, build_pack, port, ...	Spin up a new app from Git	1 API call
deploy_application	app_uuid: str	Kick off a deploy; returns immediately, poll status	1 API call + build time
get_application_logs	app_uuid, tail?: int	Debug a running or failing app	1 API call
update_env_variable	app_uuid, key, value, is_preview?: bool	Change an env var; does not auto-redeploy	1 API call
create_database	engine, name, project, server, config	Provision a new managed DB (Postgres, MySQL, Redis, MongoDB, etc.)	1 API call
search_docs	query: str	Look up Coolify feature usage without leaving the chat	free

비용 및 제한

운영 비용

API 쿼터: Bounded by Coolify instance — no formal rate limit, but keep calls sane
호출당 토큰: List calls ~500-2000 tokens (optimized); detail calls ~200-1000
금액: Free, MIT. Coolify itself is free & self-hosted.
팁: Use search_docs before guessing — it's cheaper than Claude trial-and-error-ing a feature it's unsure about.

보안

권한, 시크릿, 파급범위

최소 스코프: A Coolify API token scoped to the team you want to manage

자격 증명 저장: COOLIFY_ACCESS_TOKEN env var on the machine running MCP client

데이터 외부 송신: Direct to your Coolify instance; your Coolify handles everything else

절대 부여 금지: Share the token — it's equivalent to full control of your PaaS

MCP runs with token privileges — a compromised client = full PaaS access. Use scoped tokens where Coolify supports it.
Destructive tools (delete app, delete DB) run without extra confirmation — tell Claude to always ask first.

문제 해결

자주 발생하는 오류와 해결

401 Unauthorized

Token invalid or expired. Regenerate in Coolify > Settings > API and update the env var.

확인: curl -H 'Authorization: Bearer $TOKEN' $COOLIFY_URL/api/v1/servers

Deploy stuck in 'queued'

Check if the Coolify server has free CPU/disk. Also confirm the build queue isn't blocked by a previous hung deploy.

확인: Use `list_deployments` tool and cancel stale ones

create_application returns 422 build_pack invalid

Valid values are: nixpacks, static, dockerfile, dockercompose. Case sensitive.

Custom domain shows cert error

DNS must point to the Coolify server before TLS can be issued. Verify A record, then ask Claude to trigger the LE issuance retry.

확인: dig app.example.com

대안

coolify-mcp 다른 것과 비교

대안	언제 쓰나	단점/장점
Dokploy MCP	You're on Dokploy instead of Coolify	Similar feature set; Dokploy is the closest competitor
Caprover / Dokku CLI via ssh-manager	You use Caprover or Dokku and don't have a dedicated MCP	Drive via SSH commands; less ergonomic but works anywhere

coolify-mcp