coolify
MCP server from JoshuaRileyDev/coolify-mcp-server
claude mcp add --transport stdio joshuarileydev-coolify-mcp-server node /path/to/coolify-mcp-server/dist/index.js \ --env COOLIFY_API_URL="http://localhost:8000" \ --env COOLIFY_TEAM_ID="optional-team-id" \ --env COOLIFY_API_TOKEN="your-api-token-here"
How to use
Coolify MCP Server exposes a type-safe MCP interface for managing Coolify resources through MCP clients. It provides a suite of tools to list, create, start, stop, and deploy applications; manage databases, servers, projects, and services; and query system information such as the Coolify version. You can connect via Claude Desktop or other MCP clients by configuring an MCP server entry that points to the Node-based server (dist/index.js) and by supplying the required COOLIFY_API_URL and API token. The server maps MCP actions to Coolify API operations, returning structured results that MCP clients can interpret. Tools are organized into categories (Applications, Databases, Servers, Projects, Services, System) and each tool corresponds to a specific operation, for example list_applications, get_application, deploy_application, and get_version. Resources exposed include coolify://applications, coolify://databases, coolify://servers, coolify://projects, coolify://services, and coolify://teams. This enables automated workflows, chat-based tooling, and integration with automation pipelines that need to manage Coolify resources programmatically.
How to install
Prerequisites:
- Node.js (LTS) and npm installed
- Access to a Coolify instance with API URL and token
Step-by-step:
-
Install dependencies and build: npm install npm run build
-
Set required environment variables (examples): export COOLIFY_API_URL="http://localhost:8000" export COOLIFY_API_TOKEN="your-api-token-here" export COOLIFY_TEAM_ID="optional-team-id"
-
Run the server (example using Node): node dist/index.js
-
(Optional) Run in development with tsx or via npx as described in the config: npx tsx src/index.ts
-
Verify the MCP server is reachable by an MCP client and that the available tools respond accordingly.
Additional notes
Notes and tips:
- Ensure COOLIFY_API_URL is reachable from the environment where the MCP server runs.
- The API token should have appropriate permissions (read/write as needed; full access is recommended for MCP usage).
- If using Claude Desktop, update the claude_desktop_config.json with the coolify server details and environment variables.
- For production, consider using a process manager (e.g., pm2) and securing environment variables.
- If you encounter authentication errors, re-check token scopes and rotor/team ID settings.
- The MCP server supports a range of operations across Applications, Databases, Servers, Projects, and Services; refer to the Available Tools section in the README for exact commands.
- Use the get_version tool under System to verify the server is healthy and connected to the correct Coolify instance.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.