coolify

This MCP server provides a programmable interface to your Coolify instance via the MCP protocol. It exposes tools to manage teams, servers, projects, environments, services, applications, and deployments through the Coolify API. Core capabilities include reading version and health information, listing and retrieving details for teams, servers, projects, environments, and services, and performing lifecycle operations such as creating, starting, stopping, and restarting resources. Enhanced error reporting helps you diagnose validation errors and API issues more quickly. To start using it, configure the MCP server in your MCP settings (see installation) and ensure your Coolify base URL and API token are available as environment variables. You can then invoke the provided MCP tools from your assistant or automation workflow to manage resources in Coolify programmatically.

Prerequisites:\n- Node.js 18 or higher (runtime for the MCP server)\n- npm (comes with Node.js) or npm-runner equivalent\n- Access to a Coolify instance (base URL and API token)\n\nInstallation steps:\n1) Install the MCP server globally via npm or use npx when starting:\n\n - Global install (optional):\n npm install -g coolify-mcp-server\n\n - Or run with npx directly (no global install):\n npx coolify-mcp-server &\n\n2) Prepare environment variables for Coolify access:\n - COOLIFY_BASE_URL: https://your-coolify-instance.example.com\n - COOLIFY_TOKEN: your_generated_api_token\n\n3) Run the MCP server (example using npx as shown in the README):\n\n npx coolify-mcp-server\n\n4) If you need to run inside a script or container, ensure the same environment variables are passed to the process.\n\nPrerequisites recap:\n- Node.js 18+ installed\n- Access token with read, write, and deploy permissions on Coolify\n- Base URL of your Coolify instance\n\nNote: If you prefer Windows CMD usage in MCP settings, you can wrap the command as shown in the README:\n\n command: cmd\n args: ["/c", "npx", "-y", "coolify-mcp-server"]

Tips and common considerations:\n- Ensure COOLIFY_BASE_URL is reachable from the environment where the MCP server runs.\n- Keep COOLIFY_TOKEN secure; rotate tokens periodically and limit token permissions to only what’s needed (read, write, deploy).\n- If you encounter version compatibility issues, verify that the Coolify API version matches the server’s supported range in the README.\n- When running behind a proxy, configure HTTP(S)_PROXY environment variables for the MCP server to reach Coolify.\n- In MCP settings, you can customize the server name (e.g., coolify) and provide an alternative Windows-friendly command sequence if needed.\n- Use the available tools described in the README (e.g., list_projects, create_application, start_service) to automate workflows and integrate Coolify management into your automation pipelines.