Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COOLIFY_TOKEN | Yes | Your Coolify API token with read, write, and deploy permissions | |
| COOLIFY_BASE_URL | Yes | The base URL of your Coolify instance |
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 |
|---|---|
| get_versionA | Get Coolify version information. Returns the current version of the Coolify instance. |
| health_checkA | Check Coolify API health status. Note: This endpoint may not be available in all Coolify versions. |
| list_teamsA | List all teams the authenticated user has access to. Use this to get team UUIDs needed for other operations. |
| get_teamA | Get details of a specific team. Requires a team ID obtained from list_teams. |
| get_current_teamA | Get details of the currently authenticated team. This is the team associated with your API token. |
| get_current_team_membersB | Get a list of all members in the currently authenticated team. Shows who has access to team resources. |
| list_serversA | List all servers registered in your Coolify instance. Use this to get server UUIDs needed for other operations. |
| create_serverB | Create a new server in Coolify. Requires SSH access details and a private key for authentication. |
| validate_serverB | Validate a server's configuration and connectivity. Use this to verify server setup and troubleshoot connection issues. |
| get_server_resourcesB | Get a list of applications and services running on a server. This provides an overview of all resources deployed on the specified server. |
| get_server_domainsB | Get a list of domains configured for a server. These domains are used for routing traffic to applications and services. |
| list_projectsB | List all projects accessible by the current user. Projects organize applications and services into logical groups. |
| get_projectC | Get details of a specific project including its environments. |
| create_projectC | Create a new project to organize applications and services. |
| list_environmentsB | List all environments in a project. Environments separate different deployment stages like production, staging, development. |
| create_environmentC | Create a new environment within a project. |
| list_servicesA | List all services across your Coolify instance. Services are containerized applications running on your servers. |
| create_serviceA | Create a new service on a specified server. Services are containerized applications that run on your Coolify servers. Either "type" or "docker_compose_raw" must be provided - you cannot specify both. |
| start_serviceC | Start a previously created service. This will initialize the service container and make it accessible. |
| stop_serviceA | Stop a running service. This will gracefully shut down the service container. |
| restart_serviceB | Restart a service by stopping and starting it again. Useful for applying configuration changes or recovering from issues. |
| list_applicationsA | List all applications across your Coolify instance. Applications are deployable units sourced from Git repositories. |
| create_applicationC | Create a new application in Coolify. Applications are deployable units that can be sourced from Git repositories. |
| start_applicationB | Start a previously created application. This will initialize the application container and make it accessible. |
| stop_applicationA | Stop a running application. This will gracefully shut down the application container. |
| restart_applicationA | Restart an application by stopping and starting it again. Useful for applying configuration changes or recovering from issues. |
| execute_command_applicationA | Execute a command inside a running application container. Useful for debugging, maintenance, or running one-off tasks. Note: This endpoint may not be available in all Coolify versions. |
| get_application_logsB | Get application logs by UUID. Essential for debugging and monitoring application behavior, errors, and performance issues. Retrieve logs from running applications to troubleshoot deployment issues and monitor application health. |
| list_deploymentsA | List all deployments across your Coolify instance. Deployments represent the history of application and service deployments. |
| get_deploymentB | Get detailed information about a specific deployment. Use this to monitor deployment status and troubleshoot issues. |
| list_private_keysA | List all SSH private keys stored in Coolify. These keys are used for server authentication and Git repository access. |
| create_private_keyB | Create a new SSH private key in Coolify for server authentication or Git repository access. |
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 32 tools
Most tools have distinct purposes targeting specific resources (applications, services, servers, projects, teams) and actions (create, get, list, restart, start, stop), with clear boundaries. However, some overlap exists between application and service tools (e.g., restart_application vs restart_service) that could cause confusion if the distinction between 'applications' and 'services' isn't fully understood, though descriptions help clarify.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_application, list_servers, get_project, restart_service, and stop_application. All tools use snake_case without deviations, making them predictable and easy to parse for agents.
With 32 tools, the count is borderline high for a deployment management server, potentially feeling heavy and overwhelming. While it covers many operations, it might include redundant or overly granular tools that could be consolidated, such as separate start/stop/restart for applications and services.
The tool set provides comprehensive CRUD and lifecycle coverage for the Coolify domain, including creation, listing, retrieval, management (start/stop/restart), logging, deployment tracking, and validation. No obvious gaps exist; it supports full workflows from server setup to application deployment and monitoring.