Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Dokploy MCP

NPM · @VIBETOOLS/DOKPLOY-MCP · 2 COMPONENTS · SCANNED AUG 3

Dokploy MCP server for Codex, Cursor, and Claude with compact stdio and hosted HTTP modes

+48 this week 72 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to vcode-sh/dokploy-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 641 tokens (~213/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @vibetools/dokploy-mcp

# add to Claude Code
claude mcp add vcode-sh-dokploy-mcp -- npx -y @vibetools/dokploy-mcp
# add to Codex CLI
codex mcp add vcode-sh-dokploy-mcp -- npx -y @vibetools/dokploy-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vcode-sh-dokploy-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@vibetools/dokploy-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vcode-sh-dokploy-mcp --command npx --arg -y --arg @vibetools/dokploy-mcp
# ~/.hermes/config.yaml
mcp_servers:
  vcode-sh-dokploy-mcp:
    command: "npx"
    args: ["-y", "@vibetools/dokploy-mcp"]
// mcp.json
{
  "mcpServers": {
    "vcode-sh-dokploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibetools/dokploy-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +53
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: vcode-sh/dokploy-mcp security
    • Schema quality: unverified → good functional
    • MCP protocol: unverified → pass functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Licence: MIT functional
  • 31 Jul 26 −25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +20
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: unverified functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@vibetools/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
vcode-sh/dokploy-mcp
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/vcode-sh/dokploy-mcp/.github/workflows/release.yml@refs/tags/v4.0.0
Rekor log index:
2128710117
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:b5ebd816bd1a1b2eca05521ba6a46c551677c542ee5b7f126aae7f591de25c4a22e88d942bfcdc166e6575e7d101c52ef8a2656e9d523a08b2c31f6ff
Discovery method:
attestation_endpoint
Dependencies 100 packages

100 packages in the resolved dependency tree · 98 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~641 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
execute ~290

Run JavaScript code or a guided Dokploy workflow. In code mode, write bare JS against global `dokploy` and `helpers` without wrapping it in a function. In workflow mode, `deploy-application` can resolve a target, choose preview vs apply, collect bounded rollout options, and build a bounded plan when sampling and elicitation are enabled. When MCP tasks are enabled, execute also supports polling and cancellation for long-running runs. Known Dokploy IDs yield reusable `dokploy://...` resource links, and `search` helps discover procedures.

NameTypeReqDescription
codestringJavaScript code. `dokploy` and `helpers` are globals -- do NOT wrap in a function. Simple: `await dokploy.project.all()`. Multi-step: `const app = await dokploy.application.one({ applicationId: "abc"…
profilestringDokploy profile name. Required when DOKPLOY_PROFILES_JSON configures multiple profiles.
workflowobjectOptional guided workflow mode. Currently supports `deploy-application` with interactive target resolution, preview/apply selection, bounded rollout options, and an MCP-native plan when phase 3 sampli…

No output schema declared.

No examples provided.

list_profiles ~40

List the available Dokploy profiles, including default and named targets, without exposing API keys. Returns profile names, normalized Dokploy API URLs, and config sources.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~311

Search the Dokploy API catalog. IMPORTANT: Do NOT wrap code in a function -- `catalog` is already a global. Write bare code: `catalog.searchText("deploy")` or `catalog.recommend("safe database password rotation")` or `catalog.getByTag("application")` or `catalog.get("application.one")`. Common patterns: `catalog.recommend("tail project logs across environments")` -> helper-first workflow suggestions; `catalog.get("application.one")` -> application detail fields plus optional shaping params; `catalog.get("application.update")` -> build/runtime/resource tuning fields such as byte-based memory limits; `catalog.get("application.many")` -> batched application reads; `catalog.get("project.overview")` -> compact project state view; `catalog.get("deployment.all")` -> deployment history entries. Returns procedure names, parameters, HTTP methods, schemas, and response hints for key endpoints.

NameTypeReqDescription
codestringyesJavaScript code. `catalog` is a global -- do NOT wrap in a function. Examples: `catalog.searchText("application deploy")` | `catalog.recommend("safe database password rotation")` | `catalog.getByTag(…
profilestringOptional Dokploy profile name to validate before returning catalog results.

No output schema declared.

No examples provided.