coolify

Coolify

Use this skill when working with Coolify Cloud or a self-hosted Coolify instance.

Before Acting

1. Confirm the task affects the intended Coolify instance, project, environment, and resource.
2. Prefer read-only discovery first: health, current team, projects, servers, and resources.
3. Never print API tokens, private keys, password values, environment variable values, raw secrets, IPs, or credentials unless the user explicitly asks and the task requires it.
4. Treat deployments, starts, stops, restarts, deletes, env changes, private key changes, cloud token changes, API enable/disable, MCP enable/disable, server creation, and domain overrides as mutating operations.
5. For destructive or broad mutating operations, restate the exact target UUID/name and proceed only when the user's request is already clear.

Connection

Assume the plugin may already have a saved local connection. If a tool reports missing token configuration, expired credentials, or a wrong instance, switch to the coolify-setup skill and help the user connect Coolify. Do not ask the user to paste secrets into chat.

Tooling Strategy

Use MCP tools from the coolify server when available. In Codex tool names this normally appears as the mcp__coolify namespace, with the tool names below:

• coolify_health: verify instance health and version.
• coolify_config_status: check saved connection state without revealing secrets.
• coolify_list: list common resources.
• coolify_get: inspect one resource.
• coolify_lifecycle: start, stop, or restart apps, services, and databases.
• coolify_deploy: trigger deployments by UUID or tag.
• coolify_deployment_history: list deployment history for one application or all applications.
• coolify_application_logs: fetch application logs.
• coolify_envs: manage environment variables.
• coolify_openapi_search: find less common endpoint details.
• coolify_request: call any relative /api/v1 endpoint.

For endpoints not covered by named tools, call coolify_openapi_search first, then use coolify_request with the path, query, and body shape from the bundled OpenAPI spec.

If tool_search cannot find mcp__coolify or the named Coolify tools even though the plugin was referenced, switch to the coolify-setup skill. Do not simulate Coolify operations from repo-local scripts for marketplace users. A failed thread may have stale plugin capability metadata, so the recovery path is reinstall/update plus a brand-new top-level thread, not a same-thread retry or fork.

Common Workflows

Instance Inventory

1. Run coolify_health.
2. Run coolify_request for /teams/current.
3. List project, server, resource, application, service, and database as needed.
4. If the user asks about deployments they "have" or deployment history, run coolify_deployment_history; do not rely on coolify_list with kind: "deployment" alone.
5. Summarize names, UUIDs, status, domains, servers, deployment counts, and project/environment relationships.

Deployment

1. Identify the exact resource UUID or deployment tag.
2. Check current resource status and recent deployments with coolify_deployment_history.
3. Run coolify_deploy.
4. Poll deployments or fetch application logs if the user wants follow-up.

Environment Variables

1. Use coolify_envs with action: "list" first.
2. Keep values redacted by default.
3. For creates or updates, use action: "create", action: "update", or action: "bulk_update".
4. Do not delete variables unless the user explicitly requested deletion.

Logs and Troubleshooting

1. Inspect the resource and its server.
2. Fetch recent application logs with an appropriate line count.
3. Check deployments for failed or running jobs.
4. Use coolify_request for server validation, domains, backups, scheduled task executions, or specific API endpoints after finding them in OpenAPI.

API Notes

• Coolify API base path is /api/v1.
• Authentication uses Authorization: Bearer <token>.
• Common resource identifiers are UUIDs. Team endpoints use numeric IDs.
• /health may be available outside /api/v1; the MCP health tool handles both forms.
• GET /deployments lists currently running deployments, not all historical deployments.
• Historical application deployments live at GET /deployments/applications/{uuid}. Use coolify_deployment_history for user-facing deployment inventories.
• GET /deploy triggers deployment by UUID or tag. Coolify also accepts deployment parameters in other forms, but prefer the tool unless OpenAPI lookup says otherwise.
• Environment variable list responses can contain sensitive fields. Keep default redaction on unless raw values are required.

Safety Defaults

• Use least-privilege tokens.
• Avoid logging secrets.
• Prefer exact UUIDs over fuzzy names for mutating calls.
• If a domain conflict or force override appears, surface the conflict and ask for confirmation before proceeding.
• If Coolify returns a 401 or 403, explain that the token may be missing, expired, scoped too narrowly, or associated with the wrong team.