Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to coolify-mcp

No user-submitted related servers found.

    Related Servers

    • coolify-mcp

      jurislm
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Coolify infrastructure management, providing 45 tools for servers, applications, databases, deployments, and diagnostics via natural language.
      32 npm
      MIT

    • Coolify MCP Server

      forsonny
      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
      215 npm
      7
      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

    • 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
      42 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 136 tools

    Disambiguation3/5

    The resource-prefixed tool families (application/service/database/server) are mostly distinct, but several tools overlap or are inconsistently qualified. For example, coolify_get_logs and coolify_list_envs apply specifically to applications while database/service variants are explicitly named, and backup/storage/import tools across resources can be confused. An agent can usually infer intent, but the volume of parallel triplets creates real misselection risk.

    Naming Consistency4/5

    The overwhelming majority of tools follow a predictable coolify_verb_noun pattern in snake_case, with clear resource qualifiers like coolify_list_application_scheduled_tasks. Minor deviations exist, such as coolify_healthcheck, coolify_get_logs, and coolify_trigger_deploy, which are less structurally consistent than the rest.

    Tool Count2/5

    136 tools is far too many for practical agent selection, even for a broad platform like Coolify. Many operations are repeated across applications, services, and databases in parallel triplets, and consolidation into resource-scoped or parameterized tools would substantially reduce the surface.

    Completeness5/5

    The surface covers lifecycle operations across applications, databases, services, servers, projects, environments, storages, backups, deployments, previews, scheduled tasks, GitHub Apps, registries, teams, private keys, and instance settings. CRUD, start/stop/restart, logs, backup/import, and deployment control are all represented, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources