Coolify
Operate self-hosted Coolify apps, run diagnostics, and search docs from your agent with a large optimized tool surface.
Overview
Coolify MCP is an MCP server for the Operate phase that provides 38 tools to manage Coolify infrastructure, run diagnostics, and search documentation from your agent.
What is this MCP server?
- 38 optimized MCP tools for Coolify APIs and workflows
- Diagnostics helpers for troubleshooting live deployments
- Built-in Coolify documentation search from the agent
- npm package @masonator/coolify-mcp with stdio transport
- Requires COOLIFY_ACCESS_TOKEN and optional COOLIFY_BASE_URL
- 38 optimized MCP tools per published server description
- Package version 2.7.3 (@masonator/coolify-mcp)
- Two environment variables: required COOLIFY_ACCESS_TOKEN and COOLIFY_BASE_URL
Community signal: 420 GitHub stars.
What problem does it solve?
Toggling between the Coolify UI and your agent breaks flow when you need quick deploy fixes, resource checks, or doc lookups on a self-hosted stack.
Who is it for?
Solo builders self-hosting on Coolify who want MCP-driven ops, troubleshooting, and doc retrieval from Claude Code or Cursor.
Skip if: Teams on Vercel-only or serverless-only workflows with no Coolify instance, or anyone unwilling to issue a Coolify API access token.
What do I get? / Deliverables
Your agent invokes Coolify API operations, diagnostics, and doc search in one MCP session tied to your instance token.
- Agent-driven Coolify resource and ops actions
- Diagnostic tool results for live stack issues
- Doc search answers grounded in Coolify documentation tooling
Recommended MCP Servers
Journey fit
Coolify management is day-two hosting work—deployments, services, and instance health—after the product exists, which aligns with Operate and self-hosted infra control. The server targets infrastructure orchestration on your Coolify instance, not feature coding; Infra is the canonical shelf for PaaS-style ops from the agent.
How it compares
Coolify-specific infra MCP with 38 tools, not a generic LSP or proposal-memory server.
Common Questions / FAQ
Who is Coolify MCP for?
It is for developers who run workloads on their own Coolify server and want their coding agent to manage and diagnose that environment via the official API.
When should I use Coolify MCP?
Use it when deploying changes, inspecting services, debugging production issues on Coolify, or looking up Coolify docs while iterating on infra.
How do I add Coolify MCP to my agent?
Install @masonator/coolify-mcp (npm), set COOLIFY_ACCESS_TOKEN and COOLIFY_BASE_URL, and register the stdio MCP server in your client configuration.