Summary

Not a read-only view of your Coolify: it provisions servers, creates databases and triggers deploys.

The coverage runs the whole way down — a conversation can create the Hetzner server, put a project and environment on it, deploy an application from a private repository, and add the Postgres it needs. That reach is also the caution: the same token that reads logs can delete an application, so scope it the way you would any deploy credential.

What it is

Full coverage of the Coolify v4 REST API as tools — servers, projects, environments, applications, databases, services, deployments and the keys behind them.

What you get

Applications created the way you actually deploy: from a public repository, a private one via GitHub App or deploy key, a Dockerfile, a Docker image, or Docker Compose
Lifecycle control on anything running — start, stop and restart applications, databases and services — plus application logs
Environment variables managed per application, database or service, including a bulk update for applications
Databases provisioned by engine: PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly or ClickHouse, with backups created and their executions listed
Deployments listed globally or per application, triggered by tag or UUID, inspected and cancelled mid-flight
Infrastructure below the apps: servers created, validated, updated and deleted, with their resources and domains, and Hetzner servers provisioned directly using the location, type, image and SSH key lookups
Projects and environments as the organising layer, each with the full create, read, update and delete set
Persistent storage and scheduled tasks attached to an application or service
The credentials layer: private keys, GitHub Apps with their repository lists, and cloud tokens
Teams and their members, the API version, and a health check that needs no authentication

Requirements

A running Coolify v4 instance and an API token from Security → API Tokens, with COOLIFY_BASE_URL and COOLIFY_TOKEN in the environment. Node.js 18 or higher; published on npm as coolify-mcp-server and run over stdio. Three tools — enable_api, disable_api and validate_server — need Coolify v4.2.0 or newer, and the API-toggle tools need a root token.

Setup effort

One command plus a key — npm install -g coolify-mcp-server, then supply credentials