Skip to main content
Glama
sapientsai

dokploy-mcp-server

by sapientsai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to dokploy-mcp-server

No user-submitted related servers found.

    Related Servers

    • @sattva/dokploy-mcp

      sattva2020
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Dokploy that dynamically generates 420+ tools from the Dokploy OpenAPI spec, enabling deployment, management, and monitoring of self-hosted infrastructure through AI assistants.
      20 npm
      1
      MIT

    • Dokploy MCP Server

      firebaseStudio
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to manage Dokploy infrastructure (Docker, projects, applications, databases, etc.) through natural language, acting as a universal translator between AI and cloud systems.
      23 npm
      MIT

    • 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.
      19 npm
      MIT

    • easypanel-mcp

      dray-supadev
      A
      license
      B
      quality
      C
      maintenance
      MCP server for EasyPanel that enables AI agents to manage servers, projects, services, databases, and domains via 40 curated tools or raw tRPC access to all 347 API procedures.
      42
      15 npm
      4
      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

    A3.6/5.0

    Scored across 28 tools

    Disambiguation4/5

    Nearly every tool targets a distinct resource domain, and descriptions carefully separate near-neighbors like `dokploy_backup` vs `dokploy_volume_backup`. A few overlaps remain—`info` vs `dokploy_settings` version/health, and `dokploy_docker.pruneBuildCache` vs `dokploy_settings clean dockerBuilder`—so agents could mis-select in those edge cases.

    Naming Consistency4/5

    Names follow a consistent `dokploy_<resource>` snake_case convention, with nested prefixes like `dokploy_docker_volume` and `dokploy_docker_image`; sub-action verbs (create/update/remove/list) are also consistent. The bare `info` tool and noun-only module names like `dokploy_settings` are deviations from a strict verb_noun pattern, but the overall scheme remains predictable.

    Tool Count2/5

    With 28 top-level tools, the set exceeds the 25+ threshold and creates a heavy selection burden for agents. Although the Dokploy platform is broad, some tools could be consolidated (settings/info, docker/image/volume, overview/search), making the count feel higher than necessary.

    Completeness4/5

    The surface covers the full deployment lifecycle: projects, environments, applications, composes, databases, deployments, backups, domains, DNS, networks, volumes, registries, SSH keys, schedules, and audit logs. Missing user/role, git-provider, and notification management tools are notable gaps, since the audit log implies those resource types exist.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources