Skip to main content
Glama
forsonny

Coolify MCP Server

by forsonny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Coolify MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      2 npm
      2
      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

    • 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
      72 npm
      MIT

    • coolify-mcp

      frndchagas
      A
      license
      B
      quality
      A
      maintenance
      MCP server for Coolify API that enables full deployment workflows from zero to production, including project, server, and application management.
      65
      82 npm
      3
      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.4/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between application and service operations. No ambiguity between tool purposes.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern, but there is a mix of 'get_' and 'list_' for retrieval operations (e.g., get_server_domains vs list_applications), which is a minor inconsistency.

    Tool Count3/5

    35 tools is on the high side, but the server covers multiple domains (applications, services, environments, servers, etc.). It could be streamlined slightly but is not excessive.

    Completeness2/5

    Notable gaps: missing delete operations for applications and services, no update for application/service properties (only envs), and no explicit deploy or redeploy tools for deployments. This will likely cause agent failures for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources