A local connection that lets the coding agent manage Coolify, a tool for deploying and operating applications on servers. It provides 38 tools for infrastructure management, diagnostics, and searching Coolify's documentation.

It helps manage Coolify infrastructure, diagnose problems, and look up Coolify documentation. It requires a Coolify access token and server address.

It lets the agent work with Coolify from your development setup instead of requiring separate manual steps.

coolify — MCP server by StuMason

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/stumason/coolify-mcp/coolify

Clone the repo

git clone --depth 1 https://github.com/StuMason/coolify-mcp

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

coolify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

server.json · 13 lines

What it actually says

{
  "coolify": {
    "command": "npx",
    "args": [
      "-y",
      "@masonator/coolify-mcp"
    ],
    "env": {
      "COOLIFY_ACCESS_TOKEN": "",
      "COOLIFY_BASE_URL": ""
    }
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 13 lines scan A cf12984125c8

Subscribe to this mod's changes

coolify is an MCP server published in the GitHub repository StuMason/coolify-mcp (570 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Cloud DevOps and cloud ai claude coolify mcp model-context-protocol

awesome-coolify

Coolify 4.1.x MCP server — deploy, diagnose, and manage apps, services, and databases. Runs locally from the awesome-coolify-mcp npm package.

clezcoding/awesome-coolify · not measured

coolify-mcp

MCP server implementation for Coolify. Runs locally from the @jurislm/coolify-mcp npm package.

jurislm/coolify-mcp · not measured

kastell

MCP server "kastell" as configured in kastelldev/kastell. Runs ${CLAUDE_PLUGIN_ROOT}/../../dist/mcp-bundle.mjs with node. Needs 5 environment variables to run.

kastelldev/kastell · not measured

mcp

MCP server for Run402 — full-stack backend infrastructure for AI agents: Postgres, auth, storage, serverless functions and atomic deploys. Paid with x402/MPP. Includes $0.03 image generation. Runs locally from the run402-mcp npm package. Needs 2 environment variables to run.

kychee-com/run402 · not measured

ionoscloud-mcp

MCP server "ionoscloud-mcp" as configured in ionos-cloud/ionoscloud-mcp. Runs in Docker (ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.0). Needs 4 environment variables to run.

ionos-cloud/ionoscloud-mcp · not measured

ionoscloud

MCP server "ionoscloud" as configured in ionos-cloud/ionoscloud-mcp. Launched with ionoscloud-mcp. Needs 2 environment variables to run.