Skip to main content
Glama
HaroldXd

Dokploy MCP

by HaroldXd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Dokploy MCP

No user-submitted related servers found.

    Related Servers

    • helipod-mcp by helipodapp

      helipod-mcpofficial

      helipodapp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding tools to deploy apps and databases, run VPS servers, buy domains and edit DNS, and send email through natural-language requests across Container, VPS, Domain, and Email APIs.
      MIT
    • Roar AI MCP Server by Roar-AI-Labs

      Roar AI MCP Serverofficial

      Roar-AI-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to deploy and manage hosted apps from git repos, read logs, add Postgres databases and domains, manage API keys and budgets, and send requests to 200+ AI models. Connects over remote Streamable HTTP with OAuth sign-in, so users need no API keys, installs, or local server.
      MIT
    • PlugLayer MCP Server by pluglayer

      PlugLayer MCP Serverofficial

      pluglayer
      A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT

    • cloudflare-mcp-server

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.
      1,914 npm
      Apache 2.0
    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.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (cloudflare_records vs cloudflare_zones, upsert vs delete, catalog vs call). Minor overlap exists between dns_check and cloudflare_records (both inspect DNS) and between application_env_patch and the generic dokploy_call, but descriptions clarify the boundaries.

    Naming Consistency3/5

    A clear cloudflare_* prefix group exists, but conventions are mixed: some names are noun-first (cloudflare_records, dokploy_catalog) while others are verb-first (cloudflare_upsert, cloudflare_delete, dns_check), and standalone tools lack a prefix. Readable but not a single predictable pattern.

    Tool Count5/5

    Nine tools is well-scoped for a server spanning Dokploy orchestration and Cloudflare DNS. The catalog/call gateway collapses many potential endpoints into two tools, keeping the surface lean.

    Completeness4/5

    Cloudflare DNS covers list zones, list records, upsert, delete, and a resolver check, and Dokploy is broadly covered via the catalog+call passthrough plus a targeted env patch. Only minor gaps (e.g. zone creation or richer Dokploy shortcuts) remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources