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 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_versionB | 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_applicationsB | 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_deploymentsB | 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_keysB | 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrediam/coolify-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server