Publisher: XCO Agency (Shopify Plus Partner)
Cursor marketplace plugin for Coolify's built-in Model Context Protocol server. It does not reimplement Coolify APIs.
- MCP lives on your instance:
{COOLIFY_BASE_URL}/mcp - Transport: Streamable HTTP
- Auth:
Authorization: Bearer <team API token> - Docs: Set up MCP · How MCP works · Cursor client
mcp.json— remote MCP URL + Bearer header via plugin variables- Skills: setup, inspect, deploy
INSTALL-GROKBOT.md— AddMcpServer / multi-team notes
Each installer uses their own Coolify instance and team token. No shared infrastructure.
- A Coolify Cloud or self-hosted instance with a public HTTPS URL
- Instance MCP enabled (Settings → Configuration → Advanced → API and MCP)
- Team MCP enabled for the team that owns the token
- API token with at least
read(adddeployonly if you need lifecycle tools)
Install coolify, then set plugin variables:
| Variable | Required | Notes |
|---|---|---|
COOLIFY_BASE_URL |
yes | Origin only, no trailing slash (e.g. https://app.coolify.io) |
COOLIFY_API_TOKEN |
yes | Team-scoped token from Keys & Tokens |
{
"mcpServers": {
"coolify": {
"url": "${COOLIFY_BASE_URL}/mcp",
"headers": {
"Authorization": "Bearer ${COOLIFY_API_TOKEN}"
}
}
}
}Or paste the absolute URL and Bearer header in Cursor → Settings → Tools & MCP → New remote MCP server.
Create one token per Coolify team (e.g. staging vs production). Install two MCP entries with different names and tokens. See INSTALL-GROKBOT.md.
Ask the assistant to call get_current_team or get_infrastructure_overview. The response should match the team bound to your token.
- Prefer least privilege (
readunless you needdeploy) - Never commit tokens; rotate if they leak
- MCP does not return full env values or full deployment logs (see Coolify docs)
- Revoking the API token immediately cuts off MCP access for that client
MIT — see LICENSE. Coolify itself remains under its own license.
XCO Agency — Shopify Plus Partner. Built and maintained for the Cursor / agent ecosystem.