MCP server for Coolify — 44 optimized tools for infrastructure management, diagnostics, and documentation search
Coolify MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for Coolify — 44 optimized tools for infrastructure management, diagnostics, and documentation search.
Manage Coolify from Claude, Cursor, or any MCP client: 44 consolidated tools for deploying, debugging, and operating your self-hosted PaaS in plain English.
Once Coolify is connected, these are the calls the assistant has available:
Category — ToolsInfrastructure — get_infrastructure_overview, get_mcp_version, get_version, system (health, list_resources, enable/disable API)Diagnostics — diagnose_app, diagnose_server, find_issuesServers — list_servers, get_server, validate_server, server_resources, server_domainsProjects — projects (list, get, create, update, delete via action param)Environments — environments (list, get, create, delete via action param)Applications — list_applications, get_application, application (CRUD + delete_preview)Databases — list_databases, get_database, database (create 8 types, delete), database_backups (CRUD schedules, executions incl. delete)Services — list_services, get_service, service (create, update, delete, list_containers; per-container update_application + start/stop/restart_applicationControl — control (start/stop/restart for apps, databases, services)Logs — logs (container logs for app, database, service; services need container), application_logs (superseded by logs)Tags — tags (list, attach, detach for apps, databases, services; tag resources then deploy them together; Coolify v4.2+)Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 3 environment variables: COOLIFY_BASE_URL, COOLIFY_ACCESS_TOKEN, DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Coolify's toolset — Category, Infrastructure, Diagnostics and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Category | Tools |
| Infrastructure | get_infrastructure_overview, get_mcp_version, get_version, system (health, list_resources, enable/disable API) |
| Diagnostics | diagnose_app, diagnose_server, find_issues |
| Servers | list_servers, get_server, validate_server, server_resources, server_domains |
| Projects | projects (list, get, create, update, delete via action param) |
| Environments | environments (list, get, create, delete via action param) |
| Applications | list_applications, get_application, application (CRUD + delete_preview) |
| Databases | list_databases, get_database, database (create 8 types, delete), database_backups (CRUD schedules, executions incl. delete) |
| Services | list_services, get_service, service (create, update, delete, list_containers; per-container update_application + start/stop/restart_application, Coolify v4.2+) |
| Control | control (start/stop/restart for apps, databases, services) |
| Logs | logs (container logs for app, database, service; services need container), application_logs (superseded by logs) |
| Tags | tags (list, attach, detach for apps, databases, services; tag resources then deploy them together; Coolify v4.2+) |
| Storages | storages (list, create, update, delete persistent/file storages for apps, databases, services) |
| Deployments | list_deployments, deploy (incl. wait-to-terminal-status), deployment (get, cancel, list_for_app) |
**Any MCP client (JSON config):**
```json
{
"mcpServers": {
"coolify": {
"command": "npx",
"args": ["-y", "@masonator/coolify-mcp"],
"env": {
"COOLIFY_BASE_URL": "https://your-coolify-instance.com",
"COOLIFY_ACCESS_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| COOLIFY_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| COOLIFY_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.