Skip to main content
Glama

Related Servers

Alternatives to Coolify Creation MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage self-hosted Coolify v4 instances, including listing applications, safely handling environment variables with masking and dry runs, deploying, restarting, and reading logs.
      20
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to deploy and manage applications on Coolify through structured tools, supporting project management, app lifecycle control, pre-configured templates, and deployment monitoring with built-in safety guardrails.
      416 npm
      3
      MIT
    • 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
      15 npm
      3
      MIT
    • A
      license
      B
      quality
      C
      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
      11 npm
      28
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct action and application type. The plan_* and create_* pairs are clearly differentiated by validation versus writing, and the two get_* tools cover inventory and webhook retrieval.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_*, plan_*, and create_*. The application-type suffixes are predictable and readable.

    Tool Count5/5

    Twelve tools are well-scoped for a creation-focused MCP. The plan/create pairs map cleanly to five supported application sources, with two supporting inspection tools.

    Completeness4/5

    The surface covers creation across Docker Image, public Git, GitHub App, deploy key, and inline Dockerfile applications, plus preflight context and webhook retrieval. It intentionally omits deployment triggering and update/delete operations, which are reasonable gaps for a creation-focused server but may limit follow-up workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data