LabscoMCP early access ↗
JoshuaRileyDevMCP SERVER

Coolify MCP Server by JoshuaRileyDev

Run the everyday Coolify controls from an agent: list, start, stop, restart and deploy applications, create projects, databases and servers, and start or stop services.

PaaS Deployment & App HostingCommunity

LABSCO SUMMARY

A short set of everyday Coolify controls, and nothing in it deletes.

The tools cover the daily loop — see what is on the instance, deploy, start, stop and restart — plus creating projects, databases and servers; none of them removes anything. create_database takes only a name and a type, so anything beyond that is set in Coolify itself. The README recommends a full-access token for this server, and Coolify's token scopes also include read-only, for when the agent should only look.

What it is

A Coolify client with 18 tools across applications, databases, servers, projects and services, plus read-only resources that list each of those and your teams.

What you get

  • Applications: list_applications, get_application, create_application from a name with an optional Git repository and branch, and deploy_application, optionally at a tag.
  • Runtime control for applications: start_application, stop_application and restart_application, each by application ID.
  • Databases: list_databases, and create_database with a name and a type such as postgresql, mysql, mongodb or redis.
  • Servers: list_servers, create_server with a name, IP address, SSH port and user, and validate_server to check the connection.
  • Projects: list_projects, and create_project with a name and description.
  • Services: list_services, start_service and stop_service.
  • get_version for the version of the Coolify instance.

Requirements

A reachable Coolify instance and an API token for it: the address goes in COOLIFY_API_URL and the token in COOLIFY_API_TOKEN, both required; COOLIFY_TEAM_ID is optional. Create the token in Coolify under Keys & Tokens > API tokens.

Setup effort

Add the configuration to your client