Coolify MCP server

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

• applicationEnvs

  Manage environment variables for an application. Actions: list (secrets masked unless showSecrets), create, update, upsert (create or update by key), bulk_update (pass envs array), delete (needs env_uuid).

• cancelDeploymentwrite action

  Cancel a running deployment by UUID.

• controlDatabase

  Start, stop, or restart a database by UUID.

• controlService

  Start, stop, or restart a service by UUID.

• createApplicationwrite action
• createDatabasewrite action

  Create a database. `type` selects the engine: postgresql, mysql, mariadb, mongodb, redis, keydb, dragonfly, or clickhouse. Requires project_uuid, server_uuid, and environment_name or environment_uuid (one is enough). Engine-specific fields (versions, credentials, memory limits, ...) can be passed in `extra` and are validated per engine.

• createEnvironmentwrite action

  Create a new environment in a project. Requires the project UUID.

• createPrivateKeywrite action

  Create a new SSH private key. The private_key field should contain the full PEM-encoded key.

• createProjectwrite action

  Create a new Coolify project. Returns the project UUID.

• createServerwrite action

  Create a new server. Requires a private key UUID for SSH access.

• createServicewrite action

  Create a one-click service (database, cache, etc.) or a Docker Compose deployment (pass docker_compose_raw with the YAML content). Requires project_uuid, server_uuid, and environment_name (or environment_uuid). Since Coolify v4.1, Docker Compose deployments are services, not applications.

• databaseBackups

  Manage scheduled backups for a database. Actions: list, create, update, delete (backup schedules), list_executions, delete_execution. create/update take frequency (cron expression) plus optional fields (enabled, save_s3, s3_storage_uuid, databases_to_backup, dump_all, retention settings via extra).

• databaseEnvs

  Manage environment variables for a database. Actions: list (secrets masked unless showSecrets), create, update, bulk_update (pass envs array), delete (needs env_uuid).

• deleteApplicationwrite action

  Delete an application by UUID. Optionally delete volumes, configurations, and connected networks.

• deleteDatabasewrite action

  Delete a database by UUID. By default Coolify also deletes configurations, volumes, and connected networks and runs docker cleanup; pass the flags as false to keep them.

• deletePreviewwrite action

  Delete a preview deployment of an application by pull request id.

• deletePrivateKeywrite action

  Delete an SSH private key by UUID. Not recoverable from Coolify once gone.

• deleteProjectwrite action

  Delete a project by UUID. This will delete all environments and resources in the project.

• deleteServerwrite action

  Delete a server by UUID.

• deleteServicewrite action

  Delete a service by UUID. By default Coolify also deletes configurations, volumes, and connected networks and runs docker cleanup; pass the flags as false to keep them.

• deploywrite action

  Trigger a deployment for an application by UUID or tag. With wait=true, polls until every triggered deployment reaches a terminal status (finished/failed/cancelled) and returns a log tail for failures — raise your MCP client's tool timeout when waiting on long builds.

• diagnoseApp

  Diagnose an application by UUID, name, or domain. Aggregates current status, the latest deployments, a log tail from the most recent failed deployment, recent runtime logs, and suggested next actions in one call.

• diagnoseServer

  Diagnose a server by UUID, name, or IP: lists the resources running on it with a status breakdown, configured domains, and suggested next actions.

• getApplication

  Get application details by UUID (optional field selection).

• getDatabase

  Get database details by UUID.

• getDeployment

  Get deployment status and logs by UUID.

• getGithubAppBranches

  List branches of a repository accessible to a GitHub App.

• getGithubAppRepositories

  List repositories accessible to a GitHub App.

• getHealth

  Check that the Coolify API is up (GET /health).

• getInfrastructureOverview

  One-call summary of the whole Coolify estate: servers, projects, applications (with status breakdown), databases, services, and currently running deployments.

• getLogs

  Fetch runtime logs for an application.

• getPrivateKey

  Get an SSH private key's metadata by UUID. The key material is masked unless showSecrets is true.

• getServer

  Get server details by UUID.

• getServerDomains

  List all domains configured on a server.

• getServerResources

  List all resources (applications, databases, services) running on a server.

• getService

  Get service details by UUID (secrets masked by default; pass showSecrets to reveal).

• listAppDeployments

  List deployments for an application with pagination (skip/take).

• listApplications

  List all Coolify applications.

• listDatabases

  List databases with optional pagination and filters.

• listDeployments

  List currently running deployments.

• listEnvironments

  List all environments for a project. Requires the project UUID.

• listGithubApps

  List all configured GitHub Apps. Used for private repository access.

• listPrivateKeys

  List all SSH private keys. Keys are used for server authentication and deploy keys.

• listProjects

  List all Coolify projects. Returns project UUID, name, description, and environments.

• listResources

  List Coolify resources with optional pagination, summary, and filters.

• listServers

  List all Coolify servers. Returns server UUID, name, IP, user, port, and proxy type.

• listServices

  List all Coolify services (one-click apps like databases, caches, etc.).

• redeployProject

  Trigger a deployment for every application in a project (optionally a single environment). Asks for confirmation on clients that support elicitation.

• restartApplication

  Restart an application by UUID.

• restartProjectApps

  Restart every application in a project (optionally a single environment). Asks for confirmation on clients that support elicitation.

• scheduledTasks

  Manage scheduled tasks (cron jobs) for an application or service. Actions: list, create (name, command, frequency), update, delete, list_executions (all but list/create need task_uuid).

• searchDocs

  Full-text search across the official Coolify documentation using a local index bundled with this server (no network). Returns page titles, canonical coolify.io/docs URLs, and snippets.

• serviceEnvs

  Manage environment variables for a service. Actions: list (secrets masked unless showSecrets), create, update, bulk_update (pass envs array), delete (needs env_uuid).

• startApplication

  Start an application by UUID. Optionally force rebuild.

• stopAllApplications

  Stop every running application, optionally restricted to one project. Asks for confirmation on clients that support elicitation, stating the blast radius.

• stopApplication

  Stop an application by UUID.

• storages

  Manage persistent volumes and file mounts for an application, database, or service. Actions: list, create, update, delete. create needs storage type ('persistent' or 'file') and mount_path; update targets storage_uuid; delete needs storage_uuid.

• teams

  Read Coolify teams. Actions: list, current, current_members, get (needs id), members (needs id).

• updateApplicationwrite action

  Update an application's configuration by UUID. Common fields are exposed; any other Coolify application field (install/build/start commands, health checks, resource limits, static flags, ...) can go in `extra` and is validated against the OpenAPI schema.

• updateDatabasewrite action

  Update a database's configuration by UUID. Common fields are exposed; any other Coolify database field can go in `extra`.

• updatePrivateKeywrite action

  Update an SSH private key. The Coolify API identifies the key by its private_key content (required); name and description are optional.

• updateProjectwrite action

  Update a project's name or description.

• updateServerwrite action

  Update a server by UUID. Common fields are exposed; any other Coolify server field can go in `extra`.

• updateServicewrite action

  Update a service by UUID. Common fields are exposed; any other Coolify service field (docker_compose_raw, connect_to_docker_network, ...) can go in `extra`.

• validateServer

  Validate server connection and configuration by UUID.

• Code scan35 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 qualitystatic API keys via environment variables6/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 65% of 48,273 servers

Tools

65

the typical server has 7

Tools that change things

34%

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

GitHub stars

4

more than 82% of 28,534 servers

Downloads a week

150

more than 71% of 11,915 servers with a package

Coolify MCP: common questions

Is Coolify MCP server safe?

Mostly: it is graded B (83/100). Read the Coolify MCP safety report

How do I install Coolify MCP?

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

Does Coolify MCP need an API key?

Yes. The registry entry asks for COOLIFY_TOKEN.

Is Coolify MCP maintained?

The last commit was 7 days ago (2026-10-26). The latest release is v2.3.1.

How does Coolify MCP compare with other MCP servers?

safety score 83/100 (higher than 65% of 48,273 servers); tools 65 (the typical server has 7); tools that change things 34% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.