Skip to main content
Glama
FelixAllistar

Coolify MCP Server

by FelixAllistar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Coolify MCP Server

No user-submitted related servers found.

    Related Servers

    • Coolify MCP Server

      JoshuaRileyDev
      A
      license
      B
      quality
      D
      maintenance
      Enables management of Coolify instances to control applications, databases, and servers through the Model Context Protocol. It provides a comprehensive set of tools for deploying services and monitoring self-hosted infrastructure using natural language.
      18
      8 npm
      3
      MIT

    • Coolify MCP Server

      kof70
      A
      license
      B
      quality
      B
      maintenance
      Enables control and management of Coolify self-hosted PaaS instances, allowing you to deploy applications, manage databases, monitor servers, and execute operations directly from AI assistants.
      89
      8 npm
      29
      MIT

    • Coolify MCP Server

      HowieDuhzit
      A
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to interact with Coolify for complete infrastructure management including applications, databases, servers, deployments, and team operations. Provides 100% API coverage with 64 tools for managing the entire Coolify ecosystem through natural language.
      18
      7 npm
      6
      MIT

    • Coolify MCP Server

      StuMason
      F
      license
      A
      quality
      F
      maintenance
      Enables interaction with Coolify applications and resources through the Coolify API via a standardized interface, supporting application management operations such as listing, starting, stopping, restarting, and deploying.
      11
      13
      -
    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

    D1.5/5.0

    Scored across 10 tools

    Disambiguation2/5

    The tool names identify broad resource areas, but several overlap conceptually, such as services vs. applications and system vs. config-status. With no descriptions, agents have little basis to determine which tool is appropriate for a given task.

    Naming Consistency3/5

    Most tool names follow a simple lowercase-hyphenated plural noun pattern, but there is no consistent verb-noun structure and there are outliers like ping, system, and config-status. The naming is readable but not a strong unified convention.

    Tool Count4/5

    Ten tools is a reasonable count for a server focused on managing infrastructure resources. However, the lack of descriptions makes it difficult to confirm that each tool earns its place in the set.

    Completeness2/5

    The surface appears to be read-oriented resource access rather than full lifecycle coverage, with no obvious create, update, or delete operations. Tools like private-keys and config-status hint at configuration management, but the set likely leaves agents unable to perform common management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources