Coolify MCP: Back From the Dead

When MCP was first released and I was vibe coding through everything with Cursor, I quickly made a Coolify MCP. Mostly so Claude could debug issues with applications on my server, set env vars, that sort of thing.

But I left it to rot the moment something bad happened and Cursor couldn't get me out of it.

Recently I've been playing with Coolify more, debugging deployments, which meant I needed my MCP back. Rather than vibe coding the fix (Opus 4.5 could have done that), I wanted to spec code the update - get it to do exactly what I wanted in the exact way I wanted.

Turns out that wasn't completely possible. 70+ tools (Coolify has an extensive API) took well over 4GB to build. But I got around 50 of the most important tools running really smoothly.

What It Does

The Coolify MCP gives Claude direct access to your Coolify infrastructure. No more digging around in tabs copying over env names and horrible 08g070g0g07800g34343gwo UUIDs.

Debugging & Monitoring: Pull application logs in real-time to diagnose crashes. Check deployment status and history. Get detailed info about any app, database, or service. List all resources running on a server. Validate server connections when things go sideways.

Environment & Configuration: Create, update, delete environment variables. Update application settings (domains, branches, basic auth). Modify service configs including docker-compose updates. Manage projects and environments.

Deployment Control: Start, stop, restart applications, databases, services. Trigger deployments with optional force rebuilds. Check deployment progress and history.

Real Example

Today I used it to add HTTP basic auth to a Glances monitoring service. What would normally be:

1. SSH into the server
2. Find the docker-compose file
3. Work out Traefik's label escaping requirements
4. Generate htpasswd hashes
5. Update the compose file
6. Restart the service
7. Test it actually worked

Became: "Add basic auth (admin:password) to my Glances service."

Claude handled all the escaping nightmares, generated the correct htpasswd hash, updated the service, restarted it, and verified it worked. Five minutes instead of twenty.

Getting Started

Install via npm:

npx @modelcontextprotocol/create-server coolify-mcp

Configure with your Coolify instance URL and API token. Done.

Makes debugging broken builds and connection issues so. much. easier.