Skip to main content
Glama
frndchagas

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to coolify-mcp

No user-submitted related servers found.

    Related Servers

    • coolify-mcp

      jimrarras
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing a self-hosted Coolify instance. Provides full REST CRUD, deploy/watch capabilities, and an optional host-ops tier for live log streaming, SSH, Docker, and database access.
      22
      8 npm
      MIT

    • coolify-mcp-server

      Softtor
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Coolify API integration, enabling management of applications, databases, services, servers, and deployments via Claude Code or any MCP-compatible client.
      5 npm
      2
      MIT

    • Coolify MCP Server

      wrediam
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides integration with the Coolify API, enabling DevOps teams to manage Coolify deployments, applications, services, and servers through MCP tools.
      32
      164 npm
      46
      MIT

    • awesome-coolify-mcp

      clezcoding
      A
      license
      A
      quality
      A
      maintenance
      One MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.
      19
      32 npm
      MIT

    • coolify-mcp

      jurislm
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Coolify infrastructure management, providing 45 tools for servers, applications, databases, deployments, and diagnostics via natural language.
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 65 tools

    Disambiguation3/5

    Most tools are clearly resource-specific, but several overlap: listDeployments/listAppDeployments, getServerResources/listResources/diagnoseServer, and getLogs/getDeployment all deal with related deployment or resource information. Descriptions help, but an agent could easily misselect between the summary and diagnostic tools.

    Naming Consistency3/5

    Verb-first camelCase naming dominates, but the pattern is broken by noun-only bundle tools like applicationEnvs, databaseBackups, storages, scheduledTasks, and teams. The generic control verb in controlDatabase and controlService is also a minor inconsistency, though the overall naming remains readable.

    Tool Count2/5

    65 tools is well beyond the typical well-scoped range and creates navigation overhead. The broad Coolify domain justifies some size, but many list/query/diagnostic tools could be consolidated, and the count calibration explicitly marks 25+ as too many.

    Completeness4/5

    The surface covers most lifecycle operations across projects, servers, private keys, applications, databases, services, deployments, environment variables, storages, and scheduled tasks. Minor gaps exist—there is no getProject, no update/delete environment, and Github App/team management is read-only—but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources