Awesome Coolify MCP server

Read from the package source without running it. The installed server may list more.

• application

  Application lifecycle, deploy, and log actions (get, start, stop, restart, deploy, logs) \u2014 list via resource tool. Full-projection reads mask sensitive keys (password/token/secret/private/env) as *** by default; pass reveal: true to retrieve plaintext only when needed \u2014 do not persist revealed secrets. Log line content is not masked and may contain secrets printed by the application; do

• database

  Database CRUD and lifecycle (get, start, stop, restart, create, update, delete, delete_preview) \u2014 list via resource tool. create: 8 engines via engine discriminator; instant_deploy defaults true. update: curated engine-specific fields; is_public: true requires confirm: true. delete requires confirm: true with safe defaults (delete_volumes/delete_configurations/docker_cleanup/delete_connected_

• deployment

  List per-app deployments, get deployment details (status, commit, timestamps, optional capped inline logs), or cancel an in-flight deployment. Full-projection get masks sensitive keys as *** by default; pass reveal: true for plaintext only when needed \u2014 do not persist revealed secrets. Cancel on an already-terminal deployment returns { cancelled: false, already_finished: true, status } \u2014

• diagnose

  Synthesizes diagnose views for applications and servers, or runs a global fleet scan. Full-projection app diagnose masks sensitive keys in raw_application as *** by default; pass reveal: true for plaintext only when needed \u2014 do not persist revealed secrets. Server action triggers validate with a non-blocking side-effect (D-10).

• docs

  Search static Coolify documentation guides

• emergency

  Emergency and bulk operations (stop_all, redeploy_project, restart_project). High-impact destructive actions \u2014 require explicit confirm: true to execute. Call without confirm first to preview would_affect and sample_uuids; ask the human before retrying with confirm: true. Always ask the human before setting wait: true on redeploy_project.

• environment

  Environment CRUD (list, get, create, delete, delete_preview) scoped to a parent project \u2014 no update action (Coolify API has no PATCH). list accepts project_uuid XOR project_name; name multi-match \u2192 COOLIFY_AMBIGUOUS_MATCH (D-12). get/delete accept uuid XOR name within the parent project scope (D-13). create with a duplicate name returns COOLIFY_409 with a recovery hint (D-15). delete req

• meta

  MCP server metadata (version)

• private_key

  Private key CRUD (list, get, create, update, delete, delete_preview) for SSH keys registered in Coolify. PEM material is never returned by any action \u2014 full projection masks the private_key field even with reveal:true (D-02). list accepts reveal on the schema but rejects reveal:true at the handler with COOLIFY_422 (D-11) \u2014 PEM material is never returned. delete requires confirm:true (D-1

• project

  Project CRUD (list, get, create, update, delete, delete_preview) for Coolify organizational containers. create requires initial_environment (required \u2014 no default; agent must ask user for production vs custom name per D-09/D-10) \u2014 missing/empty \u2192 COOLIFY_422 with recovery hint; response returns { project, environment, environments? } (D-11); the auto-spawned production env is never

• resource

  Unified resource listing and cross-type discovery

• server

  Server CRUD + validate (get, create, update, delete, delete_preview, validate). Servers are listed via resource tool with type=server (D-10). create auto-validates SSH reachability with a 30s poll unless validate:false (D-05/D-06); unreachable hosts return ok:true with validation.reachable:false and a COOLIFY_SSH_UNREACHABLE recovery hint \u2014 no auto-rollback (D-07). validate uses the same wait

• service

  Service CRUD and lifecycle (get, start, stop, restart, deploy, create, update, delete, delete_preview) \u2014 list via resource tool. create: one-click type XOR compose/compose_file; instant_deploy defaults true. update: curated fields + transparent compose I/O; HTTP 409 domain conflicts include recovery hint to retry with force_domain_override: true. delete requires confirm: true with safe defaul

• system

  System actions for Coolify (health, version, verify)

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 1,119 Developer tools servers

Tools

14

the typical Developer tools server has 7

Tools that change things

0%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

34

more than 19% of 436 Developer tools servers with a package

Awesome Coolify: common questions

Is Awesome Coolify MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Awesome Coolify safety report

How do I install Awesome Coolify?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Awesome Coolify need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Awesome Coolify maintained?

The last commit was 46 days ago (2026-09-19). The latest release is v0.1.2.

What can I use instead of Awesome Coolify?

Servers from other publishers that do the same job: Aiven MCP server, Dockhold MCP server and walkerOS Flow MCP server.

How does Awesome Coolify compare with other Developer tools MCP servers?

safety score 92/100 (higher than 90% of 1,119 Developer tools servers); tools 14 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.