@vibetools/dokploy-mcp

MCP server for Dokploy.

The pitch is simple:

• default public surface: search and execute
• actual Dokploy coverage underneath: generated, broad, and tested
• less schema spam in context
• real support for creating, updating, deploying, reading logs, and wiring domains

Most MCP servers dump a warehouse of tool schemas into your context window and call it product. This one tries not to be embarrassing.

Need proof instead of a sales monologue? Start with docs/live-e2e-proof.md.

Current Fact Snapshot

• Generated API procedures in the pinned catalog: 524
• Generated tags: 48
• Default public MCP tools: 2 (search, execute)
• Default tools/list footprint from the current budget check: about 1,485 tokens (5,941 bytes)
• Reduction versus the classic endpoint-per-tool baseline (92,354 tokens): 98.4%

	Classic endpoint-per-tool baseline	Current Code Mode default
Tool definitions sent	about 92,354 tokens	about 1,485 tokens
Public MCP tools	hundreds of endpoint schemas	2
Context window tax	wide schema dump	compact fixed surface

Quick Start

Get your API key from Dokploy Settings > Profile > API/CLI.

If your client uses a JSON-style MCP config, this is the whole block:

{
  "mcpServers": {
    "dokploy": {
      "command": "npx",
      "args": ["@vibetools/dokploy-mcp"],
      "env": {
        "DOKPLOY_URL": "https://panel.example.com",
        "DOKPLOY_API_KEY": "your-api-key"
      }
    }
  }
}

If your client uses CLI-based MCP management:

# Codex
codex mcp add dokploy \
  --env DOKPLOY_URL=https://panel.example.com \
  --env DOKPLOY_API_KEY=dokp_... \
  -- npx @vibetools/dokploy-mcp

# Claude Code
claude mcp add --transport stdio \
  -e DOKPLOY_URL=https://panel.example.com \
  -e DOKPLOY_API_KEY=dokp_... \
  dokploy -- npx @vibetools/dokploy-mcp

Already authenticated with the Dokploy CLI or local dokploy-mcp config?

You may not need the env block at all.

Want the wizard path instead of manual config?

npx @vibetools/dokploy-mcp setup

Pick Your Client

• Docs Home
• Getting Started
• Cursor
• Codex
• Claude Code
• Claude Desktop

What You Actually Get

• search: discover Dokploy procedures and contracts
• execute: run multi-step workflows in one sandboxed call
• optional raw mode: one tool per procedure
• optional hybrid mode: Code Mode plus selected raw tools
• optional hosted HTTP path with server.json metadata and header-based remote auth

If you are new, use the default mode and stop overthinking it.

Read These Next

• docs/getting-started.md
• docs/guides/modes.md
• docs/guides/compose.md
• docs/guides/hosted-http.md
• docs/guides/troubleshooting.md
• docs/live-e2e-proof.md

CLI

npx @vibetools/dokploy-mcp
npx @vibetools/dokploy-mcp serve-stdio
npx @vibetools/dokploy-mcp serve-http
npx @vibetools/dokploy-mcp setup
npx @vibetools/dokploy-mcp version

Development

git clone https://github.com/vcode-sh/dokploy-mcp.git && cd dokploy-mcp
npm install
npm run build
npm run lint
npm test
npm run docs:check:facts

The rest lives in docs, where it belongs.

Credits

Forked from Dokploy/mcp. Started at 67 tools, mass-refactored to 377, then rebuilt the whole thing into an architecture that makes the tool count irrelevant.

Mauricio Siu built Dokploy itself -- the PaaS this server talks to. Without the platform, this is a very elaborate way to POST into the void.

Henrique Andrade wrote the original MCP server. 15 commits, every PR merged. The kind of contributor who closes issues instead of opening them.

Contributors who shaped the original: Joshua Macauley -- lucasleal-developer -- Nour Eddine Hamaidi -- Corey -- Azil0ne

Unmerged PRs are still blueprints. That's how open source works -- stolen inspiration with better commit messages.

License

MIT - Vibe Code

Original work by Henrique Andrade under Apache 2.0 -- see LICENSE-ORIGINAL.