MCP server for Coolify API integration
Coolify mcp server lets Claude, Cursor and other MCP clients work with Coolify directly. MCP server for Coolify API integration.
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.
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.
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.
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.
This listing has no verified copy-paste launch configuration. Use the project documentation to confirm the entry point, runtime and authentication before registering it in your MCP client. A package name or repository alone is not a runnable configuration.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
| Variable | Description | Required |
|---|---|---|
| COOLIFY_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| COOLIFY_BASE_URL | Endpoint or connection string the server talks to. | Yes |
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.