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

Dokploy MCP

NPM · @VIBETOOLS/DOKPLOY-MCP · 2 COMPONENTS · SCANNED SEP 20

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

Available components

remote · {remotehost}{mcppath} 0 npm · @vibetools/dokploy-mcp 91
0 this week 91 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • 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 72 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • 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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Dokploy MCP server?

Dokploy MCP runs locally as an npm package, launched with npx -y @vibetools/dokploy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @vibetools/dokploy-mcp

# add to Claude Code
claude mcp add vcode-sh-dokploy-mcp -- npx -y @vibetools/dokploy-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "vcode-sh-dokploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibetools/dokploy-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vcode-sh-dokploy-mcp": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vcode-sh-dokploy-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@vibetools/dokploy-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vcode-sh-dokploy-mcp -t stdio -c npx -a -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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Security disclosure: unverified → pass ▲ functional
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: pass → unverified ▼ functional
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 20 Sept 2026 · Analysed npm/@vibetools/dokploy-mcp@4.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
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

Background: How many MCP packages publish verified provenance →

Dependencies 101 packages
Packages resolved 101
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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
codestring–JavaScript 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"…
profilestring–Dokploy profile name. Required when DOKPLOY_PROFILES_JSON configures multiple profiles.
workflowobject–Optional 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(…
profilestring–Optional Dokploy profile name to validate before returning catalog results.

No output schema declared.

No examples provided.

Common questions

What is the Dokploy MCP server?

Dokploy MCP is listed in the public MCP registry as io.github.vcode-sh/dokploy-mcp. Dokploy MCP server for Codex, Cursor, and Claude with compact stdio and hosted HTTP modes. This page covers its npm package (@vibetools/dokploy-mcp).

Is the Dokploy MCP server safe to use?

Dokploy MCP scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Dokploy MCP server expose?

Dokploy MCP exposes 3 tools: search, execute, list_profiles. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.

Is the Dokploy MCP server still maintained?

Dokploy MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Dokploy MCP server under?

Dokploy MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.