Coolify MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Coolify API and deployment-tool changes because actions affect hosted services

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Operating and troubleshooting Coolify infrastructure with policy-aware read and write tools.

What we know

Third-party Coolify v4 MCP with diagnostics, deployments, application/database/service/project/environment management, backups and configuration.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)chore(deps): bump the minor-and-patch group across 1 directory with 3…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Coolify role/token scope; Member role is documented read-only. Writes: Deploy/start/stop workloads; Create/update/delete infrastructure resources; Change env/config/backups.
Coolify API token plus remote-client auth when exposed.
Sensitive access: API token, Environment secrets, Infrastructure logs

Admin-capable tokens can mutate production infrastructure; least-privilege Coolify roles materially reduce risk.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

603 repository stars

Stars observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Which deployment operations and approval boundaries are documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Admin-capable tokens can mutate production infrastructure; least-privilege Coolify roles materially reduce risk.
Coolify role/token scope; Member role is documented read-only.
Coolify API token plus remote-client auth when exposed.
Infrastructure configuration, secrets and logs are handled by the server.
Reviewed write actions: Deploy/start/stop workloads; Create/update/delete infrastructure resources; Change env/config/backups
Sensitive access: API token, Environment secrets, Infrastructure logs
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Requires a Coolify v4 instance and API token.
Remote HTTP and local stdio have different auth boundaries.
Member-role tokens in current docs are read-only.

Original activity observations

2026-10-05T11:08:28Z: chore(deps): bump the minor-and-patch group across 1 directory with 3…

Technical identity

github.com/stumason/coolify-mcp

Exact implementation source: https://github.com/stumason/coolify-mcp ↗
Reviewed resource type: MCP Server
Repository identity: stumason/coolify-mcp
Package identity: npm:@masonator/coolify-mcp
Service endpoint: https://your-domain/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

GitHub repository ↗
stumason/coolify-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Coolify MCP connects to a running Coolify v4 service via its API token.
publisher documented step · Publisher instructions
claude mcp add coolify -e COOLIFY_BASE_URL="https://your-coolify-instance.com" -e COOLIFY_ACCESS_TOKEN="your-api-token" -- npx @masonator/coolify-mcp@latest
publisher setup or prerequisite · Publisher instructions
npx @masonator/coolify-mcp doctor
Configure / authenticate
MCP100 setup guide
Choose either `.mcpb` Claude Desktop extension, local `claude mcp add coolify ...` configuration, or remote OAuth HTTP endpoint. Configure Coolify URL/token where needed.
Previously reviewed local API-token configuration; remote OAuth is separate: Requires running Coolify v4 and API token. Claude Desktop can install official coolify-mcp.mcpb. Claude Code may use included command; Cursor JSON uses npx package @masonator/coolify-mcp with COOLIFY_BASE_URL and COOLIFY_ACCESS_TOKEN. Codex uses its own `codex mcp add` and --env syntax, not Claude Desktop JSON.
Check connection
Suggested check
Publisher `npx @masonator/coolify-mcp doctor` checks token and Coolify reachability; do not deploy as a verification step.
Remove / uninstall / revoke
MCP100 setup guide
For local Claude Code registration use `claude mcp remove coolify`; remove the .mcpb from Claude Desktop Settings > Extensions if installed as a bundle. For remote Docker deployment stop/delete the Coolify application separately; disconnecting the OAuth client will not stop the server.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove coolify

Official Documentation & Sources

What it does

Third-party Coolify v4 MCP with diagnostics, deployments, application/database/service/project/environment management, backups and configuration.

Capability: Cloud & DevOps
Resource type: MCP Server
Best fit: Operating and troubleshooting Coolify infrastructure with policy-aware read and write tools.

Representative uses

Diagnose apps and servers
Deploy/start/stop/restart/rollback workloads
Manage apps/databases/services/projects
Manage env vars, backups and schedules

Limitations

Requires a Coolify v4 instance and API token.
Remote HTTP and local stdio have different auth boundaries.
Member-role tokens in current docs are read-only.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Coolify API token plus remote-client auth when exposed.
Permissions: Coolify role/token scope; Member role is documented read-only.
Data handling: Infrastructure configuration, secrets and logs are handled by the server.
Cost: unknown
Risk and cautions: Admin-capable tokens can mutate production infrastructure; least-privilege Coolify roles materially reduce risk.

Access scope and cautions

Write actions: Deploy/start/stop workloads Create/update/delete infrastructure resources Change env/config/backups
Sensitive access: API token Environment secrets Infrastructure logs
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Diagnose apps and servers; Deploy/start/stop/restart/rollback workloads; Manage apps/databases/services/projects; Manage env vars, backups and schedules.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx @masonator/coolify-mcp@latest. Recorded endpoint: https://your-domain/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: COOLIFY_BASE_URL; COOLIFY_ACCESS_TOKEN; MCP_AUTH_TOKEN/OAuth config for remote mode as documented. No configuration values are supplied here. Prerequisites: Node/npm; Coolify v4. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Coolify API token; remote clients use a separate inbound auth layer.

Can it modify data or perform write operations?

Documented write actions include: Deploy/start/stop workloads; Create/update/delete infrastructure resources; Change env/config/backups. Recorded permission boundary: Coolify role/token scope; Member role is documented read-only.

What data-handling boundary should I consider?

Infrastructure configuration, secrets and logs are handled by the server. Recorded sensitive-access context: API token; Environment secrets; Infrastructure logs.

What limitations and risks should I check before use?

Admin-capable tokens can mutate production infrastructure; least-privilege Coolify roles materially reduce risk. Requires a Coolify v4 instance and API token. Remote HTTP and local stdio have different auth boundaries. Member-role tokens in current docs are read-only. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Stu Mason is listed as Community implementation in MCP100’s current evidence.