Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_application_managementC | Comprehensive application management: deploy, get info, list, check status, start/stop/restart, or create applications |
| coolify_environment_configurationC | Manage environment variables, configure domains, and retrieve application logs |
| coolify_system_managementC | System management: list servers, teams, services, or test connectivity |
| coolify_documentationB | Access Coolify documentation: search docs, get topic info, API reference, or troubleshooting guides |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: application management, documentation access, environment configuration, and system management. The descriptions specify unique scopes (e.g., deploy apps vs. manage environment variables vs. system-level operations), making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent 'coolify_*' prefix with descriptive noun phrases (e.g., 'application_management', 'documentation', 'environment_configuration', 'system_management'). This uniform pattern enhances readability and predictability, with no deviations in style or convention across the set.
With 4 tools, the count is well-scoped for a Coolify management server, covering core domains like applications, documentation, environment, and system. Each tool earns its place by addressing a distinct aspect of the platform, avoiding bloat or thin coverage, which is typical for a focused set of 3-15 tools.
The tool set provides comprehensive coverage for key Coolify operations, including CRUD-like actions for applications (deploy, manage), environment configuration, system management, and documentation access. A minor gap exists in not explicitly covering update or delete for non-application resources (e.g., servers or teams), but agents can likely work around this with the available tools.