Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Health check server port | 3000 |
| NODE_ENV | No | Environment mode | development |
| COOLIFY_BASE_URL | No | Coolify API base URL | https://app.coolify.io/api/v1 |
| COOLIFY_API_TOKEN | Yes | Your Coolify API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coolify_systemB | System management operations - health check, version, and system information |
| coolify_teamsC | Complete team management - list teams, get current team, get team details, and list team members |
| coolify_projectsC | Project CRUD operations - list, create, get, update, and delete projects |
| coolify_project_environmentsC | Project environment management - list, create, get, and delete project environments |
| coolify_applicationsC | Application CRUD operations - list, create, update, get, and delete applications of all types |
| coolify_application_lifecycleC | Application lifecycle management - start, stop, and restart applications |
| coolify_application_envsC | Application environment variables management - list, create, bulk update, and delete environment variables |
| coolify_logsC | Application logs and monitoring - get application logs |
| coolify_application_deploymentsC | Application deployment management - list, get, and trigger deployments |
| coolify_databasesC | Database CRUD operations - list, create, get, update, and delete databases |
| coolify_database_lifecycleC | Database lifecycle management - start, stop, and restart databases |
| coolify_database_typesC | Specific database type creation - create PostgreSQL, MySQL, MongoDB, and Redis databases with type-specific parameters |
| coolify_serversC | Server CRUD operations - list, create, get, update, and delete servers |
| coolify_server_managementC | Server operations and resources - validate server connection, list domains, and list resources |
| coolify_servicesC | Service CRUD operations - list, create, get, update, and delete services |
| coolify_service_lifecycleC | Service lifecycle management - start, stop, and restart services |
| coolify_service_envsC | Service environment variables management - list, create, update, bulk update, and delete environment variables |
| coolify_security_keysC | Security keys management - list, create, get, update, and delete security keys |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.