Skip to main content
Glama
vcode-sh

@vibetools/dokploy-mcp

by vcode-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @vibetools/dokploy-mcp

No user-submitted related servers found.

    Related Servers

    • Dokploy MCP Server

      MCP-Mirror
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage cloud infrastructure through natural language by providing a unified interface to the Dokploy platform. Supports Docker containers, applications, databases, domains, monitoring, and deployment operations through conversational commands.
      14 npm
      1
      -

    • Dokploy MCP Server

      limehawk
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI models to interact programmatically with Dokploy servers to manage projects, applications, and deployment services. It provides 67 specialized tools for direct Dokploy API operations through the Model Context Protocol.
      167 npm
      Apache 2.0

    • @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.
      17 npm
      1
      MIT

    • dokploy-mcp

      wyattjoh
      F
      license
      Not graded
      quality
      C
      maintenance
      Wraps the Dokploy REST API to expose Dokploy operations as MCP tools for managing projects, applications, compose stacks, deployments, domains, and environment variables.
      21 npm
      1
      -
    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 3 tools

    Disambiguation4/5

    Each tool targets a different aspect: execute handles code and workflows, list_profiles lists profiles, and search queries the API catalog. Occasional overlap exists (execute and search both reference workflows) but purposes are mostly distinct.

    Naming Consistency2/5

    Naming is inconsistent: execute (bare verb), list_profiles (verb_noun with snake_case), search (bare verb). There is no clear pattern across the tool set.

    Tool Count2/5

    With only 3 tools, the server feels under-scoped for a platform like Dokploy that typically requires managing applications, deployments, and configurations. A broader tool set is expected.

    Completeness2/5

    The tool set lacks essential operations such as creating, updating, or deleting applications or deployments. While execute and search provide some flexibility, core lifecycle management is absent.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources