Coolify MCP Server

Coolify mcp server lets Claude, Cursor and other MCP clients work with Coolify directly. MCP server for Coolify API integration.

What Coolify does

The Coolify MCP (Model Context Protocol) Server is an integration layer for the Coolify API, allowing users to interact with various resources and applications through a standardized interface. This server is built using TypeScript and leverages the Model Context Protocol SDK for seamless communication.

Key capabilities

• List resources and applications
• Get details of specific applications
• Start, stop, and restart applications
• Deploy applications by tag or UUID
• Health check for system status
• Fetch the current version of the Coolify API

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

• Request — ** list-resources
• Response — ** List of all resources in Coolify
• Parameters — ** {"uuid": ""}

Installing the coolify mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: COOLIFY_ACCESS_TOKEN, COOLIFY_BASE_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Cloud and DevOps servers put infrastructure on speaking terms with your assistant, so "why is this broken?" is answered from real state rather than a generic checklist. Coolify sits in that group, and the shape of its toolset — Request, Response, Parameters — tells you what it is really for. Worth comparing against the other cloud devops servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by StuMason, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the coolify mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.