StuMason/coolify-mcp
MCP server for Coolify — 42 optimized tools for managing self-hosted PaaS through AI assistants
What it solves
It allows users to manage their Coolify self-hosted PaaS (Platform-as-a-Service) using natural language through AI clients like Claude, Cursor, or any MCP-compatible tool. It bridges the gap between a complex infrastructure management interface and an AI agent, enabling deployment, debugging, and operation of servers and applications without manual API calls or dashboard navigation.
How it works
The project implements a Model Context Protocol (MCP) server that exposes 46 specialized tools to an AI model. These tools interface with the Coolify API to perform actions such as deploying apps, reading logs, and managing environment variables. It supports three deployment modes: a one-click installation for Claude Desktop, a local installation via npx, and a remote containerized mode using HTTP/OAuth 2.1. It also includes a doctor command to verify configuration and connectivity.
Who it’s for
- DevOps engineers and developers who want to manage their infrastructure via chat.
- Agencies managing multiple Coolify instances for different clients (via "fleet mode").
- Users of self-hosted PaaS who prefer an agentic workflow for troubleshooting and deployment over a manual CLI or GUI.
Highlights
- Comprehensive Toolset: 46 tools for diagnosing apps, deploying/rolling back, creating resources, and handling configurations.
- Safety First: Destructive operations require human confirmation in supported clients, and secrets are masked at the API boundary.
- Multi-Instance Support: Ability to manage a "fleet" of multiple Coolify instances from a single connection.
- Built-in Workflows: Includes pre-defined prompts for troubleshooting applications, explaining failed deployments, and checking estate health.
- Connectivity Diagnostics: A
doctortool that identifies common configuration errors and provides one-line fixes.
Related
- Project
- Project
- Project
- Project
- Project