SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI developer platformscoolify-mcp

coolify-mcp

Manage self-hosted Coolify PaaS: deployments with verified builds, app diagnostics, database backups, offline docs search and confirmed destructive actions.

Open website

About this tool

Purpose

coolify-mcp is an MCP server based on the Coolify API, used to implement a complete deployment workflow from scratch to production on a self-hosted PaaS. It targets the Coolify v4.3.10 API, and its types and schemas are generated directly from the official Coolify OpenAPI specification, so tool inputs always stay consistent with what the API actually accepts.

Main Capabilities

  • Complete deployment workflow: Can create projects, environments, servers, and applications from scratch.
  • 5 application types: A single createApplication tool covers public git, GitHub App, Deploy Key, Dockerfile, and Docker Image sources; Docker Compose deployments are done through createService (since Coolify v4.1, compose deployments belong to services).
  • Environment management: Full CRUD for environment variables, with secret masking support.
  • Deployment control: Deploy (optionally waiting for a terminal state, with a log tail attached on failure), start, stop, and restart applications.
  • Diagnostics: diagnoseApp can find an application by UUID, name, or domain, and aggregates status, recent deployments, failure log tail, runtime logs, and suggested next actions.
  • Documentation search: searchDocs performs full-text search over the official Coolify documentation in a bundled local index, with no network required.
  • Security: Write protection, secret redaction, and MCP annotations (readOnlyHint / destructiveHint), so clients can automatically approve read operations and gate destructive calls.
  • Near-complete API coverage: Databases (8 engines, backups, environment variables), services, storage, scheduled tasks, teams, previews, servers, SSH keys, and GitHub Apps.
  • Token efficient: The definitions of 65 tools take up about ~9k tokens of context, and strict runtime validation is performed against schemas generated from the Coolify OpenAPI specification.

Usage

Before use, a Coolify API token is required (obtained in the Coolify dashboard under Settings > API).

Supported access methods include:

  • Claude Desktop one-click installation: Download coolify-mcp.mcpb from the latest release and drag it into Settings → Extensions, then fill in the Coolify URL and token as prompted, with no Node installation and no JSON editing required.
  • Claude Code CLI.
  • OpenAI Codex CLI, or edit ~/.codex/config.toml.
  • Manual configuration (~/.mcp.json).
  • Environment variable configuration.

Deployment Examples and Tool Reference

With this MCP, an application can be deployed from scratch. Tools are grouped by topic: projects and environments, servers and infrastructure, applications (read), applications (create), applications (manage), storage/scheduled tasks/previews, teams/servers/Git, and batch operations. Docker Compose deployments are created through createService with docker_compose_raw passed in, because since Coolify v4.1 they belong to services, not applications. Environment variables for databases and services have their own separate tools: databaseEnvs and serviceEnvs.

Security Features

  • Write protection: All write operations can be disabled, controlled via an environment variable.
  • Secret handling: Environment variable values are masked by default, database credentials are redacted, and showSecrets: true is used only when necessary.
  • HTTP transport hardening: The HTTP transport binds to 127.0.0.1 by default. To expose it beyond loopback, set MCP_HTTP_TOKEN; after that, every request to /mcp must carry Authorization: Bearer <token> (checked in constant time), and the binding also switches to 0.0.0.0 (can be overridden with MCP_HTTP_HOST). Binding to a non-loopback host without a token logs a prominent warning: anyone who can access that port can control your Coolify instance.
  • Destructive deletion requires human confirmation: On MCP clients that support elicitation (Claude Code, VS Code Copilot), deleting projects, applications, databases, services, servers, or private keys, it will ask for confirmation and explain what will be lost. The behavior of clients that do not support elicitation remains the same as before. Rejection, cancellation, or timeout will abort the call; setting COOLIFY_MCP_ELICITATION=off completely disables the prompt.

Version Pinning and Updates

The Coolify target version is defined in src/coolify/constants.ts. Update process: edit COOLIFY_VERSION in src/coolify/constants.ts, then run npm run generate.

Limitations and Notes

The current material does not provide pricing, charging models, performance metrics, or specific usage outcome data, so these are not available for now. Before use, ensure you have a Coolify API token, and pay attention to manual confirmation for destructive operations and secure configuration of HTTP transport.

Related tools

Browse category