Analyzed 34 days ago · 2 anonymous rescans remaining · register free to re-analyze any time.
Public analysis · read only
Register free to re-analyze

wrediam/coolify-mcp-server

42 11 1 issues
JavaScript
MIT

Project Overview

anthropic / claude-opus-4-7

Coolify MCP Server

An MCP server that exposes the full Coolify v4.1.1 REST API as tools for AI assistants.

AI Verdict
Clean— AI Trust Assessment

True Intent (AI Assessment)

Provide AI assistants with programmatic control over a Coolify self-hosting platform via the Model Context Protocol.

README Accuracy

Accurate

Notes

The test-tools.js script is misleading — it prints success messages without actually testing anything. Otherwise, stated purpose matches observed behavior and dependencies.

What Is This?

This is a Model Context Protocol (MCP) server written in TypeScript that acts as a bridge between MCP-compatible AI clients (like Claude Desktop, Windsurf, or Cline) and a self-hosted Coolify instance. It wraps Coolify's v4.1.1 REST API into a comprehensive set of callable tools, allowing an AI to manage infrastructure and applications through natural-language requests.

The problem it solves is operational friction. Coolify is a self-hosted PaaS (an open-source Heroku/Vercel alternative), and administering it normally requires clicking through a dashboard or hand-crafting API calls. This server lets users delegate those tasks — deploying apps, provisioning databases, restarting services, managing environment variables, spinning up Hetzner servers — to an AI agent via conversational commands.

The target users are DevOps engineers, indie developers, and homelab operators who already run Coolify and use AI coding assistants. They install the package via npm/npx, plug two environment variables (base URL and API token) into their MCP client config, and gain conversational control over their Coolify instance.

Architecturally, it's simple: a single TypeScript entry point (src/index.ts) uses the @modelcontextprotocol/sdk to register tool handlers and axios to make authenticated HTTP calls to Coolify's /api/v1 endpoints. It communicates with the MCP client over stdio. Coverage is broad — teams, servers, projects, environments, applications (public, private GitHub, deploy key, Dockerfile, Docker image, Docker Compose variants), databases (Postgres, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, ClickHouse), services, deployments, private keys, GitHub apps, cloud tokens, and Hetzner provisioning.

Notable observations: the codebase is essentially one large source file plus a smoke-test script (test-tools.js) that does not actually invoke tools — it just prints checkmarks, so 'test' claims should be taken with a grain of salt. Dependencies are minimal and reputable (only axios and the official MCP SDK). No obfuscation, no network calls beyond the user-configured Coolify host, no telemetry visible.

Your Report, Tab by Tab
At a Glance
42Stars
11Forks
1Open Issues
May 2026Last Active
MCP Server / CLI ToolTypeScriptMIT
Technology Stack
LanguagesTypeScript, JavaScript
RuntimeNode.js 18+
FrameworkModel Context Protocol SDK
DatabaseNone (client for external Coolify API)
Package Managernpm
Key Dependencies@modelcontextprotocol/sdk, axios
Build ToolTypeScript compiler (tsc)
Test FrameworkNone (test-tools.js is a stub script)