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.
      16 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.
      10 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.
      10 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
      18 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.8/5.0

    Scored across 28 tools

    Disambiguation4/5

    Each tool maps to a distinct Dokploy resource (application, compose, database, domain, network, etc.) with an action discriminator, so most selections are unambiguous. Minor overlaps remain: dokploy_overview vs dokploy_project list, dokploy_settings clean=dockerPrune vs dokploy_docker pruneBuildCache, and the vague grab-bag name dokploy_infrastructure (ports/auth/certs).

    Naming Consistency4/5

    Nearly all tools follow a clean dokploy_<resource> snake_case pattern (dokploy_application, dokploy_dns_provider, dokploy_volume_backup), which is predictable. The lone deviation is the unprefixed 'info' tool.

    Tool Count4/5

    28 tools is on the heavy side, but each corresponds to a genuinely separate resource in a large deployment platform, and bundling many actions under each tool keeps the surface from exploding into hundreds of entries. Slightly over the ideal 3-15 band but defensible for this scope.

    Completeness4/5

    Broad CRUD/lifecycle coverage exists for almost every resource: projects, environments, applications, compose, databases, backups, volume backups, domains, redirects, networks, DNS/vault providers, registries, destinations, SSH keys, mounts, schedules, previews, deployments, docker and settings. Some platform areas lack tools (user/custom-role management, notifications, git-provider management) even though audit-log resource types reference them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources