# @fndchagas/coolify-mcp

MCP server for Coolify — deploy, diagnose, and manage applications, databases, services, backups, and servers on your self-hosted PaaS. 64 tools generated from the official OpenAPI spec, docs search included, secrets masked by default.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2.3.1
- **Author:** Fernando Chagas
- **License:** MIT
- **npm:** @fndchagas/coolify-mcp
- **Source:** https://github.com/frndchagas/coolify-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 10 days

## Security scan

- **Status:** warnings
- **Scanned:** 2026-08-18T03:55:20.116Z
- **Version scanned:** 2.2.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `getInfrastructureOverview`
- `getHealth`
- `restartProjectApps`
- `redeployProject`
- `stopAllApplications`
- `listResources`
- `listProjects`
- `createProject`
- `listServers`
- `getServer`
- `listEnvironments`
- `createEnvironment`
- `updateProject`
- `deleteProject`
- `createServer`
- `validateServer`
- `listPrivateKeys`
- `createPrivateKey`
- `listGithubApps`
- `listApplications`
- `listDatabases`
- `listDeployments`
- `listAppDeployments`
- `getApplication`
- `getDatabase`
- `getDeployment`
- `getLogs`
- `applicationEnvs`
- `deploy`
- `cancelDeployment`
- `createApplication`
- `updateApplication`
- `deleteApplication`
- `startApplication`
- `stopApplication`
- `restartApplication`
- `listServices`
- `createService`
- `createDatabase`
- `updateDatabase`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"coolify\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@fndchagas/coolify-mcp\"\n      ],\n      \"env\": {\n        \"COOLIFY_TOKEN\": \"<YOUR_COOLIFY_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `COOLIFY_TOKEN` — Coolify Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40fndchagas%2Fcoolify-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40fndchagas%2Fcoolify-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40fndchagas%2Fcoolify-mcp
- HTML page: https://forgeregistry.com/registry/%40fndchagas%2Fcoolify-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.