coolify-setup

Coolify Setup

Install this skill pack (Cursor, Claude Code, Codex):

npx skills add clezcoding/awesome-coolify -a cursor -a claude-code -a codex

MCP prompt analog: new-project (src/mcp/prompts.ts) — primary entry is MCP setup tool per D-01.

Related skills: coolify-deploy · coolify-diagnose · coolify-incident

MCP setup tool

Primary entry: MCP setup tool (setupActionsCatalog):

• preflight() — verify GitHub CLI presence and auth (headless-safe)
• wire(mode, ...) — provision or link Coolify resources
• resume(mode?, ...) — re-run preflight after human gh auth

Safety: optional instance routing · no auto-push git by default · gh soft-pause (no in-tool poll)

Workflow

1. Preflight — call setup({ action: "preflight" }).
2. On COOLIFY_SETUP_PAUSED — stop for human action:
   • Install gh if missing: cli.github.com
   • Run gh auth login (or set GH_TOKEN / GITHUB_TOKEN for headless)
   • Do not poll or sleep inside the agent loop waiting for auth.
3. Resume — after auth succeeds, call setup({ action: "resume", ... }) with the same wire params you will use for step 4.
4. Wire — call setup({ action: "wire", mode: "greenfield" | "link-existing", ... }).

Modes

Mode	Use when
greenfield	Create new Coolify project/environment and provision via recipe
link-existing	Attach workspace to an existing Coolify project/server

Optional flags (default off)

Pass explicitly only when needed:

• include_domains — attach domains after wire (greenfield, or link-existing with application_uuid)
• set_env — sync environment variables after wire (greenfield, or link-existing with application_uuid). When enabled, pass exactly one of env_file (local .env path) or env_content (inline .env text) — no workspace auto-detect. Application resources only (not one-click services).
• deploy_and_watch — trigger deploy and bounded deployment.watch after wire (greenfield, or link-existing with application_uuid)
• push — on greenfield only; default false omits gh --push. Set push: true to push after repo create.