The Coolify MCP Server is an integration layer for the Coolify API, enabling management of resources and applications through the Model Context Protocol. With this server, you can:
List resources (applications, services, databases, deployments)
Get detailed information about specific applications using their UUID
Control application lifecycle (start, stop, restart) to manage availability
Deploy applications by tag or UUID, with options to force rebuilds
Update application settings to modify behavior and monitoring configurations
Perform health checks to monitor system status
Fetch the current version of the Coolify API for compatibility
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Coolify MCP Server list my applications"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This project is now maintained at:
Please update your bookmarks and references.
Deploy an application or service using a tag or UUID. This allows you to deploy new versions or updates to your applications.
Inputs: tag, uuid, force.
Retrieve detailed information about a specific application using its UUID. This includes the application's status, configuration, and deployment details.
Inputs: uuid (required).
Fetch a list of all applications currently managed by Coolify. This provides an overview of all deployed applications.
Inputs: no named parameters.
Fetch a list of all databases managed by Coolify. This provides an overview of all database instances.
Inputs: no named parameters.
Retrieve a list of all running deployments in Coolify. This includes details about the deployment status and history.
Inputs: no named parameters.
Retrieve a comprehensive list of all resources managed by Coolify. This includes applications, services, databases, and deployments.
Inputs: no named parameters.
Retrieve a list of all services managed by Coolify. This includes external services and microservices.
Inputs: no named parameters.
Restart a specific application using its UUID. This stops and then starts the application, applying any configuration changes.
Inputs: uuid (required).
Start a specific application using its UUID. This initiates the application and makes it available for use.
Inputs: uuid (required).
Stop a specific application using its UUID. This halts the application and makes it unavailable.
Inputs: uuid (required).
Update the settings of a specific application, such as health check configurations. This allows you to modify the application's behavior and monitoring settings.
Inputs: uuid (required), settings (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 11 tools
Most tools have distinct purposes, but there is some overlap between list-applications and list-resources, as list-resources includes applications along with other resources, which could cause confusion about which to use for listing applications. The application lifecycle tools (start, stop, restart, update) are clearly differentiated from each other and from retrieval tools.
All tool names follow a consistent verb-noun pattern using kebab-case, such as deploy, get-application, list-applications, restart-application, etc. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 11 tools, the count is well-scoped for managing applications and resources in a deployment platform like Coolify. Each tool serves a clear purpose, covering deployment, retrieval, listing, and lifecycle management without being overly sparse or bloated.
The tool set provides strong coverage for application management, including CRUD-like operations (deploy, get, update, start/stop/restart) and listing functions. However, there are minor gaps, such as no tools for creating or deleting databases or services, which might be expected in a full resource management suite, though the focus seems to be on applications.
Deploy and manage applications, databases, domains, and git repos
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Manage Fly.io apps, Machines, volumes, secrets, Managed Postgres, and Sprites with OAuth.
