Connect Coolify to Cursor
Manage applications, services, deployments, and servers. Add Toolspoke to Cursor once and it can use 19 Coolify actions. Your Coolify credential stays in Toolspoke, and you choose which actions Cursor may call.
Set it up in Cursor
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Cursor
~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }Cursor completes the sign-in in a browser tab the first time it connects.
Install Coolify and connect it
Add Coolify to a project in your Toolspoke workspace.
API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- Instance URL
- Your Coolify instance root, without /api/v1. Use https://app.coolify.io for Coolify Cloud.
- API token
- Keys & Tokens → API tokens. Grant read-only for the list actions, or read/write for deploy, power, and environment changes.
Choose what Cursor may do
All 19 actions start on. Switch off any of the 7 actions that change something in Coolify, and Cursor gets a refusal if it tries.
What you can ask Cursor for
A few of the Coolify actions that only read, so they are safe to try first.
- List the applications on this Coolify instance with their status, domain, git source, and UUID
- Read the tail of an application's container logs
- List deployments
- List one application's deployment history, newest first
What Cursor can do in Coolify
12 actions read and 7 write.
Reads
List applications
List the applications on this Coolify instance with their status, domain, git source, and UUID. Call this first, every other application action takes the UUID.
Get application
Fetch one application's full configuration: domains, build and start commands, exposed ports, health check, resource limits, and current status.
Application logs
Read the tail of an application's container logs. Use it to diagnose a crashing or unhealthy application after a deployment.
List running deployments
List deployments. Without an application UUID this returns the deployments currently running across the instance; with one it returns that application's deployment history, newest first. Build logs are omitted, use get_deployment for those.
List application deployments
List one application's deployment history, newest first. Build logs are omitted, use get_deployment for those.
Get deployment
Fetch one deployment by UUID to check whether it finished, failed, or is still building. Set include_logs to also return the build log, which can be long.
List application envs
List an application's environment variable keys. Values are masked by default because they usually hold secrets. Set reveal_values only when the caller genuinely needs a value, every tool result is written to the workspace audit log in clear text.
List servers
List the servers Coolify deploys to, with their address, SSH user, and proxy type. Returns the server UUID used by server_resources.
Server resources
List everything deployed on one server, applications, databases, and services, with each resource's current status.
List resources
List every resource on the instance in one call, applications, databases, and services together with their type and status. Use it for an instance-wide health sweep; use list_applications when you only care about applications.
List databases
List the standalone databases on this Coolify instance with their UUID, type and status. Databases that belong to a service (Chatwoot's Postgres, for example) are not standalone and are not listed. Connection URLs and passwords are dropped from the answer. Call this first for list_database_backups.
List database backups
List one standalone database's scheduled backups, each with its cron frequency, whether it uploads to S3, and its executions (status, s3_uploaded, size, filename, finished_at, message). Use it to check that the newest backup succeeded, reached S3, and is recent. Coolify matches schedules by numeric id only, so a schedule whose database_type is App\Models\ServiceDatabase belongs to a different database and should be ignored.
Writes
Update application
Change an application's configuration: how it is built, the domains it answers on, and whether it joins the predefined Docker network. Only the fields you pass are changed; everything omitted is left alone. Changes take effect on the next deployment unless you pass instant_deploy. Switching build_pack to dockercompose also needs docker_compose_location, and per-service compose domains are not settable here, read docker_compose_domains with get_application to see where they landed.
Deploy
Trigger a deployment of one or more resources, by UUID or by tag. Returns the deployment UUIDs, poll them with get_deployment. Set force to rebuild without the Docker layer cache.
Start application
Start an application's containers. Set force to rebuild without the Docker layer cache.
Stop application
Stop an application's containers, taking it offline but leaving its configuration and data intact. Use deploy when you want to ship new code instead.
Restart application
Restart an application's containers without rebuilding it.
Update application env
Update an application's existing environment variable. Call create_application_env when the key does not exist yet. The change only takes effect on the next deployment.
Create application env
Create a new environment variable on an application. Call update_application_env when the key already exists. The change only takes effect on the next deployment.
Coolify in Cursor: questions
Does Cursor see my Coolify credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Cursor only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Cursor from changing things in Coolify?
Yes. Each of the 19 actions can be switched off for a project. Turn off the 7 that change something and Cursor can only read.
Will 19 actions crowd Cursor's context?
No. Toolspoke shows Cursor five bridge tools, plus a guide where a toolkit has one, and Cursor searches for the Coolify action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Should it go in every project or just one?
Either. Put the block in ~/.cursor/mcp.json to have Toolspoke in every project, or in .cursor/mcp.json inside one project to keep it there.
What does it cost?
Tool calls are free on every plan, and a Coolify call does not run in a sandbox, so it bills nothing.
Coolify in your other apps
More infrastructure toolkits for Cursor
Try Coolify in Cursor
Free to start, and tool calls cost nothing on any plan.