Coolify MCP Server
# CoolifyMCP
[](https://cursor.com/en/install-mcp?name=coolifymcp&config=eyJjb21tYW5kIjoibnB4IGNvb2xpZnltY3AiLCJlbnYiOnsiQ09PTElGWV9BUElfVE9LRU4iOiJ5b3VyX2Nvb2xpZnlfYXBpX3Rva2VuX2hlcmUiLCJDT09MSUZZX0JBU0VfVVJMIjoiaHR0cHM6Ly95b3VyLWNvb2xpZnktaW5zdGFuY2UuY29tL2FwaS92MSJ9fQ%3D%3D)
[](https://opensource.org/licenses/MIT)
[](https://nodejs.org/)
[](https://www.typescriptlang.org/)
A comprehensive **Model Context Protocol (MCP)** server that provides complete access to all [Coolify](https://github.com/coollabsio/coolify) API endpoints. CoolifyMCP enables AI assistants to interact with Coolify for managing applications, databases, servers, deployments, and more.
> **Built for [Coolify](https://github.com/coollabsio/coolify)** - An open-source & self-hostable Heroku / Netlify / Vercel alternative
## š Table of Contents
- [Features](#-features)
- [Quick Start](#-quick-start)
- [Prerequisites](#-prerequisites)
- [Installation](#ļø-installation)
- [Configuration](#ļø-configuration)
- [Available Tools](#-available-tools)
- [Development](#ļø-development)
- [API Coverage](#-api-coverage)
- [Production Deployment](#-production-deployment)
- [Documentation](#-documentation)
- [Contributing](#-contributing)
- [License](#-license)
## ⨠Features
- **šÆ 100% API Coverage**: Complete implementation of all Coolify API endpoints
- **š ļø 18 Consolidated MCP Tools**: Streamlined access to Coolify's functionality through MCP protocol
- **š Type Safety**: Built with TypeScript for robust error handling and development experience
- **š Production Ready**: Health checks, proper logging, and monitoring
- **š¦ Modular Architecture**: Clean, maintainable codebase with separated concerns
- **š§ Comprehensive**: Supports all Coolify features including:
- š„ Team and Project Management
- š Application Lifecycle Management
- šļø Database Management (PostgreSQL, MySQL, MongoDB, Redis, etc.)
- š„ļø Server Management and Validation
- š³ Service Management
- š¦ Deployment Management
- š Environment Variables
- š Security Keys Management
## š Quick Start
### Install in Your AI IDE
CoolifyMCP works with all major AI IDEs that support the Model Context Protocol (MCP). Choose your preferred IDE:
#### **Cursor IDE** (Recommended)
1. Open Cursor and go to Settings ā Extensions ā MCP
2. Add this configuration to your `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"coolifymcp": {
"command": "npx",
"args": ["coolifymcp"],
"env": {
"COOLIFY_API_TOKEN": "your_coolify_api_token_here",
"COOLIFY_BASE_URL": "https://your-coolify-instance.com/api/v1"
}
}
}
}
```
#### **Claude Desktop**
1. Open Claude Desktop settings
2. Add this configuration to your MCP settings:
```json
{
"mcpServers": {
"coolifymcp": {
"command": "npx",
"args": ["coolifymcp"],
"env": {
"COOLIFY_API_TOKEN": "your_coolify_api_token_here",
"COOLIFY_BASE_URL": "https://your-coolify-instance.com/api/v1"
}
}
}
}
```
#### **JetBrains AI Assistant**
1. Open your JetBrains IDE (IntelliJ, WebStorm, etc.)
2. Go to Settings ā Tools ā AI Assistant ā Model Context Protocol (MCP)
3. Click "Add" and configure:
- **Name**: `coolifymcp`
- **Command**: `npx`
- **Arguments**: `["coolifymcp"]`
- **Environment Variables**:
- `COOLIFY_API_TOKEN`: `your_coolify_api_token_here`
- `COOLIFY_BASE_URL`: `https://your-coolify-instance.com/api/v1`
#### **Other MCP-Compatible IDEs**
- **LibreChat**: Add MCP server configuration in settings
- **Klavis AI**: Configure in your platform's MCP settings
- **Custom MCP Clients**: Use the same configuration format
### Local Development
```bash
# Clone and install
git clone https://github.com/howieduhzit/coolifymcp.git
cd coolifymcp
npm install
npm run build
# Run with environment variables
COOLIFY_API_TOKEN="your_token_here" COOLIFY_BASE_URL="https://your-coolify-instance.com/api/v1" npm start
```
## š Prerequisites
- **Node.js 20+** - [Download](https://nodejs.org/)
- **npm 9+** or **yarn** - Package manager
- **Coolify API token** - Get from your [Coolify dashboard](https://github.com/coollabsio/coolify)
- **Coolify instance URL** - Your Coolify instance (default: `https://app.coolify.io/api/v1`)
## š ļø Installation
### NPM Installation (Recommended)
1. Install and run with npx (no installation needed):
```bash
npx coolifymcp
```
2. Or install globally:
```bash
npm install -g coolifymcp
coolifymcp
```
### Local Development
1. Clone the repository:
```bash
git clone https://github.com/howieduhzit/coolifymcp.git
cd coolifymcp
```
2. Install dependencies:
```bash
npm install
```
3. Build the project:
```bash
npm run build
```
4. Run with environment variables:
```bash
COOLIFY_API_TOKEN="your_token_here" COOLIFY_BASE_URL="https://your-coolify-instance.com/api/v1" npm start
```
## āļø Configuration
### Environment Variables
| Variable | Description | Required | Default |
|----------|-------------|----------|---------|
| `COOLIFY_API_TOKEN` | Your Coolify API token | Yes | - |
| `COOLIFY_BASE_URL` | Coolify API base URL | No | `https://app.coolify.io/api/v1` |
| `NODE_ENV` | Environment mode | No | `development` |
| `PORT` | Health check server port | No | `3000` |
### MCP Client Configuration
The configuration format is consistent across all MCP-compatible IDEs. Here are the common locations:
#### **Configuration File Locations:**
- **Cursor**: `~/.cursor/mcp.json`
- **Claude Desktop**: MCP settings in the app
- **JetBrains**: Settings ā Tools ā AI Assistant ā MCP
- **LibreChat**: Settings ā MCP Servers
- **Custom Clients**: Refer to your client's documentation
#### **Standard Configuration:**
```json
{
"mcpServers": {
"coolifymcp": {
"command": "npx",
"args": ["coolifymcp"],
"env": {
"COOLIFY_API_TOKEN": "your_token_here",
"COOLIFY_BASE_URL": "https://your-coolify-instance.com/api/v1"
}
}
}
}
```
#### **Environment Variables:**
- `COOLIFY_API_TOKEN` (required): Your Coolify API token
- `COOLIFY_BASE_URL` (optional): Your Coolify instance URL (defaults to `https://app.coolify.io/api/v1`)
## šÆ Available Tools
The Coolify MCP Server provides **18 consolidated tools** that cover all Coolify functionality through action-based parameters:
### System Management (1 tool)
- `coolify_system` - System health, version, and information management
- Actions: `health`, `version`, `info`
### Team Management (1 tool)
- `coolify_teams` - Complete team management operations
- Actions: `list`, `current`, `get`, `members`
### Project Management (2 tools)
- `coolify_projects` - Project CRUD operations
- Actions: `list`, `create`, `get`, `update`, `delete`
- `coolify_project_environments` - Project environment management
- Actions: `list`, `create`, `get`, `delete`
### Application Management (5 tools)
- `coolify_applications` - Application CRUD operations (all types)
- Actions: `list`, `create`, `update`, `get`, `delete`
- Supports: public, private_github, private_deploy_key, dockerfile, dockerimage, dockercompose
- `coolify_application_lifecycle` - Application lifecycle management
- Actions: `start`, `stop`, `restart`
- `coolify_application_envs` - Application environment variables
- Actions: `list`, `create`, `bulk_update`, `delete`
- `coolify_logs` - Application logs retrieval
- Actions: `get`
- `coolify_application_deployments` - Application deployment management
- Actions: `list`, `get`, `trigger`
### Database Management (3 tools)
- `coolify_databases` - Database CRUD operations
- Actions: `list`, `create`, `get`, `update`, `delete`
- `coolify_database_lifecycle` - Database lifecycle management
- Actions: `start`, `stop`, `restart`
- `coolify_database_types` - Specific database type creation
- Actions: `create` (PostgreSQL, MySQL, MongoDB, Redis)
### Server Management (2 tools)
- `coolify_servers` - Server CRUD operations
- Actions: `list`, `create`, `get`, `update`, `delete`
- `coolify_server_management` - Server operations and resources
- Actions: `validate`, `domains`, `resources`
### Service Management (3 tools)
- `coolify_services` - Service CRUD operations
- Actions: `list`, `create`, `get`, `update`, `delete`
- `coolify_service_lifecycle` - Service lifecycle management
- Actions: `start`, `stop`, `restart`
- `coolify_service_envs` - Service environment variables
- Actions: `list`, `create`, `update`, `bulk_update`, `delete`
### Security Management (1 tool)
- `coolify_security_keys` - Security key management
- Actions: `list`, `create`, `get`, `update`, `delete`
## šļø Development
### Scripts
- `npm run build` - Build TypeScript to JavaScript
- `npm start` - Start the production server
- `npm run dev` - Start development server with hot reload
### Project Structure
```
coolify-mcp-server/
āāā src/
ā āāā index.ts # Main MCP server implementation
āāā dist/ # Compiled JavaScript output
āāā Dockerfile # Docker configuration
āāā docker-compose.yaml # Docker Compose configuration
āāā package.json # Dependencies and scripts
āāā tsconfig.json # TypeScript configuration
āāā config.example.env # Environment variables template
āāā README.md # This file
```
## š§ API Coverage
This MCP server provides **100% coverage** of the Coolify API with **18 consolidated tools** covering all **83+ API endpoints**:
- ā
System Management (1 tool) - Health, version, and system information
- ā
Team Management (1 tool) - Complete team operations
- ā
Project Management (2 tools) - Projects and environments
- ā
Application Management (5 tools) - All application types and lifecycle
- ā
Database Management (3 tools) - All database types and operations
- ā
Server Management (2 tools) - Server operations and resources
- ā
Service Management (3 tools) - Service operations and lifecycle
- ā
Security Management (1 tool) - Security keys and authentication
**Key Benefits of Consolidation:**
- šÆ **Reduced Complexity**: 18 tools instead of 83+ individual tools
- š **Better Performance**: Fewer tool definitions and cleaner API
- š§ **Easier Maintenance**: Action-based parameters for better organization
- š **Simplified Documentation**: Clear tool categories and actions
## š Production Deployment
### Health Checks
The server includes a health check endpoint at `/health` when running in production mode (`NODE_ENV=production`).
### Environment Configuration
For production deployment, ensure:
1. Set `NODE_ENV=production`
2. Provide valid `COOLIFY_API_TOKEN`
3. Set correct `COOLIFY_BASE_URL`
4. Configure proper logging
5. Set up monitoring and alerting
## š License
MIT License - see LICENSE file for details.
## š¤ Contributing
1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request
## š Documentation
- **README.md** - Complete documentation and usage examples
- **GitHub Repository** - Source code and issue tracking
## š Support
For issues and questions:
- š [Create an issue](https://github.com/howieduhzit/coolifymcp/issues) in the repository
- š Check the [Coolify documentation](https://coolify.io/docs)
- š¬ Join the [Coolify community](https://discord.gg/coolify)
## š Acknowledgments
This project is built for and powered by [Coolify](https://github.com/coollabsio/coolify) - an amazing open-source platform that makes self-hosting applications incredibly easy. Special thanks to the Coolify team and community for creating such a powerful tool.
- š [Coolify on GitHub](https://github.com/coollabsio/coolify) - The main Coolify project
- š [Coolify Website](https://coolify.io) - Official website and documentation
- š [Coolify Documentation](https://coolify.io/docs) - Complete documentation
- š¬ [Coolify Discord](https://discord.gg/coolify) - Community support
## š License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
---
**Built with ā¤ļø for the [Coolify](https://github.com/coollabsio/coolify) community**
[](https://github.com/howieduhzit/coolifymcp)
[](https://github.com/howieduhzit/coolifymcp)
[](https://github.com/howieduhzit/coolifymcp/issues)
---
**Powered by [Coolify](https://github.com/coollabsio/coolify)** - An open-source & self-hostable Heroku / Netlify / Vercel alternative with 45.2k+ stars āTDQS
Scored across 18 tools
Each tool has a clearly distinct purpose targeting specific resources (applications, databases, projects, servers, services, etc.) and actions (CRUD, lifecycle, envs, logs, etc.). There is no ambiguity or overlap; for example, coolify_application_envs and coolify_service_envs are clearly separated by resource type, and lifecycle tools are distinct from CRUD tools.
All tools follow a consistent 'coolify_<resource>_<action>' naming pattern with snake_case throughout. The pattern is predictable and readable, making it easy to identify the resource and operation type, such as coolify_applications for CRUD and coolify_application_lifecycle for lifecycle management.
With 18 tools, the count is slightly high but reasonable for a comprehensive server management system covering applications, databases, projects, servers, services, and more. Each tool earns its place by addressing specific aspects of the domain, though it borders on being heavy.
The tool set provides complete coverage for the Coolify domain, including CRUD operations, lifecycle management, environment variables, logs, security, and system info across all key resources (applications, databases, projects, servers, services). There are no obvious gaps; agents can perform full workflows without dead ends.