Skip to main content
Glama

Related Servers

Alternatives to coolify-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      73 npm
      3
      MIT
    • 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
    • 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
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that integrates with Coolify to let AI assistants manage Coolify instances via a clean toolkit wrapping the official REST API.
      35
      139 npm
      6
      MIT

    TDQS

    A3.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools are clearly separated by resource type (resources, deployments, storage, backups, env vars, servers, keys, projects, instances). However, deploy vs deploy_watch both trigger deployments with only blocking behavior differing, and get_servers vs list_instances could be confused, though descriptions help.

    Naming Consistency3/5

    Naming is mixed: verb_noun style (list_resources, create_resource, cancel_deployment) coexists with manage_* tools (manage_storage, manage_env, manage_projects) and unique names like control_resource, provision_hetzner. Snake_case is consistent, but the verb pattern is not uniform.

    Tool Count4/5

    22 tools is on the higher end, but Coolify is a broad platform covering resources, deployments, servers, projects, env vars, storage, backups, scheduled tasks, keys, and instances. Each tool earns its place, making the count appropriate for the scope.

    Completeness4/5

    The tool surface covers CRUD and lifecycle for most domains: resources, deployments, servers, projects, env vars, storage, backups, scheduled tasks, and keys. Minor gaps exist, such as no update_environment action and no single-deployment detail fetch (only list), but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues