Coolify MCP server

What the model can do

Coolify (Cloud or self-hosted): applications, services and databases with their status, servers, projects, scheduled tasks, and deployments running now. Can create, rename and delete projects and create environments, deploy (by resource or tag), start, restart and stop applications, services and databases, change, roll back, create (from a Docker image) and delete applications, rename and delete services, run a scheduled task, run a server's Docker clean-up, cancel a deployment, and add, replace and delete an application's environment variables.

Reads

• coolify_list_resourcesEvery application, service and database in the token's team with its status (running:healthy, exited:unhealthy…) and type (application, service…
• coolify_list_applicationsApplications: name, status, domains, git repository, branch and commit, build pack and last update.
• coolify_list_servicesOne-click and compose services: name, service type, description and when created or updated.
• coolify_list_serversServers Coolify deploys to: name, description, proxy, whether in a swarm, and how many times in a row it has been unreachable (0 means reachable).
• coolify_list_projectsProjects in the token's team: uuid, name and description.
• coolify_list_deploymentsDeployments queued or running right now (not history): application, server, status, commit and message, when started, and a link.
• coolify_list_application_envsAn application's environment variables by name only: key, uuid (for deleting), and whether build-time, runtime, preview-only, literal…
• coolify_list_databasesStandalone databases: uuid, name, engine (standalone-postgresql…), image, status (running:healthy, exited…) and last update.
• coolify_list_scheduled_tasksAn application's scheduled tasks: uuid (for coolify_execute_scheduled_task), name, whether enabled, cron frequency, container and failures in a row.

Acts, when you ask

These change something in Coolify. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• coolify_create_projectCreate a new, empty project in Coolify's current team.
• coolify_update_projectRename a Coolify project and/or replace its description.
• coolify_delete_projectDelete an empty Coolify project.
• coolify_deployDeploy by uuid (one application, service or database) or by tag (EVERY resource carrying that Coolify tag…
• coolify_start_applicationStart a stopped application: Coolify queues a deployment that brings it back up.
• coolify_restart_applicationRestart an application's containers: it is briefly unavailable while they come back.
• coolify_stop_applicationStop an application: its containers stop and it is offline until started again with coolify_start_application.
• coolify_cancel_deploymentCancel a deployment that is queued or in progress.
• coolify_create_application_envAdd an environment variable to an application.
• coolify_replace_application_envReplace the value of one or more of an application's environment variables, by key.
• coolify_delete_application_envDelete one of an application's environment variables (by its uuid from coolify_list_application_envs).
• coolify_start_serviceStart a one-click or compose service that is stopped: Coolify queues it to come up on its server.
• coolify_restart_serviceRestart a one-click or compose service: it is briefly unavailable.
• coolify_stop_serviceStop a one-click or compose service: its containers stop and it is offline until started again.
• coolify_start_databaseStart a standalone database that is stopped: Coolify queues it to come up on its server.
• coolify_restart_databaseRestart a standalone database: it is briefly unavailable and every open connection drops.
• coolify_stop_databaseStop a standalone database: its containers stop and it is offline until started again, so every application using it fails meanwhile.
• coolify_update_applicationChange an application's settings: name, description, domains (comma-separated URLs, REPLACING the current list), git branch or commit, install…
• coolify_rollback_applicationRoll an application back: Coolify queues a deployment of an earlier image tag or commit, replacing what runs now once it is healthy.
• coolify_delete_applicationDESTRUCTIVE, permanently delete an application: its containers are removed and Coolify forgets it, with its environment variables and settings.
• coolify_delete_serviceDESTRUCTIVE, permanently delete a service (every container in its compose stack): Coolify forgets it with its settings and variables.
• coolify_create_dockerimage_applicationCreate an application that runs a public Docker image, in a project environment on one server.
• coolify_update_serviceRename a Coolify service and/or replace its description.
• coolify_execute_scheduled_taskRun one of an application's scheduled tasks now, outside its schedule: Coolify queues its command in the application's container…
• coolify_run_server_docker_cleanupRun Docker clean-up on one server now: unused images and build cache are removed to free disk.
• coolify_create_environmentCreate an empty environment (such as staging) in a Coolify project.

Connect it

First connect Coolify on Dashboard → Connections, then add Memtro to your client once. The Coolify tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Coolify connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What is down in Coolify right now?
• › Which branch and commit is the Acme storefront running?
• › Is anything deploying at the moment?
• › Which server has been unreachable?
• › Roll the storefront back to yesterday's commit

Questions

Is this an official Coolify MCP server?

No. It is Memtro's MCP server with Memtro's Coolify connector behind it: the connector reads Coolify through its API with the credentials you connect on Dashboard → Connections, and Coolify publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Coolify?

Only when you ask, and only what it has been granted: create a project in Coolify; rename a Coolify project or replace its description; delete an empty Coolify project; deploy an application, service or database in Coolify, or every resource with a tag (queues a build and rollout); start a stopped application in Coolify; restart an application in Coolify (brief downtime); stop an application in Coolify (it goes offline); cancel a deployment that is queued or running in Coolify; add an environment variable to a Coolify application (takes effect on next deploy); replace the value of a Coolify application's environment variables (old values are lost); delete an environment variable from a Coolify application; start a stopped service in Coolify; restart a service in Coolify (brief downtime); stop a service in Coolify (it goes offline); start a stopped database in Coolify; restart a database in Coolify (connections drop); stop a database in Coolify (apps using it fail); change a Coolify application's name, domains, branch, commands or other settings (takes effect on next deploy); roll a Coolify application back to an earlier image or commit (queues a deployment); delete a Coolify application; delete a Coolify service; create a Coolify application from a Docker image; rename a Coolify service or replace its description; run one of a Coolify application's scheduled tasks now; run Docker clean-up on a Coolify server; create an environment in a Coolify project. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server