Coolify MCP Server

MCP (Model Context Protocol) server for Coolify API integration. Manage your applications, databases, services, servers, and deployments directly from Claude Code or any MCP-compatible client.

Features

• Multi-team support with dynamic API key configuration
• 27 tools covering all major Coolify operations
• Full TypeScript support
• Compatible with Claude Code and other MCP clients

Installation

Using npx (Recommended)

No installation required. Configure directly in your MCP settings:

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": ["-y", "@softtor/coolify-mcp-server"],
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.com",
        "COOLIFY_API_KEY": "your-api-key"
      }
    }
  }
}

Global Installation

npm install -g @softtor/coolify-mcp-server

Then configure in your MCP settings:

{
  "mcpServers": {
    "coolify": {
      "command": "coolify-mcp-server",
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.com",
        "COOLIFY_API_KEY": "your-api-key"
      }
    }
  }
}

Configuration

Environment Variables

*At least one API key must be provided.

Multi-Team Configuration

For organizations with multiple Coolify teams, configure team-specific API keys:

{
  "mcpServers": {
    "coolify": {
      "command": "npx",
      "args": ["-y", "@softtor/coolify-mcp-server"],
      "env": {
        "COOLIFY_BASE_URL": "https://your-coolify-instance.com",
        "COOLIFY_DEFAULT_TEAM": "production",
        "COOLIFY_TEAM_PRODUCTION_API_KEY": "prod-api-key",
        "COOLIFY_TEAM_STAGING_API_KEY": "staging-api-key",
        "COOLIFY_TEAM_DEV_API_KEY": "dev-api-key"
      }
    }
  }
}

Then use the team parameter in any tool:

coolify_list_applications { team: "staging" }

Getting Your API Key

1. Log in to your Coolify instance
2. Go to Settings > API Tokens
3. Create a new token with appropriate permissions
4. Copy the token and use it as your API key

Important: Tokens Are Team-Scoped

Coolify API tokens are scoped by team. Each token only provides access to resources within the team where it was created. This means:

• A token created in the "Infocell" team can only access Infocell's applications, databases, and servers
• To manage resources across multiple teams, you need a separate token for each team
• When using multi-team configuration, make sure each COOLIFY_TEAM_<NAME>_API_KEY corresponds to a token created in that specific team

See the Coolify API documentation for more details on token scopes and permissions.

Available Tools

Applications (6 tools)

Databases (6 tools)

Services (5 tools)

Servers (4 tools)

Deployments (2 tools)

Projects & Teams (4 tools)

Usage Examples

List all applications

coolify_list_applications

Deploy an application

coolify_deploy { uuid: "app-uuid-here" }

Deploy with force rebuild

coolify_deploy { uuid: "app-uuid-here", force: true }

Deploy all applications with a tag

coolify_deploy { tag: "production" }

Get application logs

coolify_get_application_logs { uuid: "app-uuid-here", since: 3600 }

Use a specific team

coolify_list_applications { team: "staging" }

Development

# Clone the repository
git clone https://github.com/Softtor/coolify-mcp-server.git
cd coolify-mcp-server

# Install dependencies
npm install

# Build
npm run build

# Run locally
COOLIFY_API_KEY=your-key npm start

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see LICENSE for details.

Related

• Coolify - Self-hostable Heroku/Netlify alternative
• Model Context Protocol - Protocol for AI tool integration
• Claude Code - Anthropic's CLI for Claude