How do I install Dokploy?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Dokploy need an API key?

The publisher lists these environment variables: DOKPLOY_URL, DOKPLOY_API_KEY, DOKPLOY_PROFILES_JSON.

When was Dokploy last checked?

Last checked 2026-10-28. MCP server for Dokploy. Two tools up front, 524 generated procedures underneath. Real deploys, less schema tax.

Servidor MCP Dokploy

Potencialize seu agente

Adicionar este servidor

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Rodar no PlugMCP

Host a copy with our keys and logs.

Server URL

https://{remoteHost}{mcpPath}

Credentials from the publisher

DOKPLOY_URL — Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL.
DOKPLOY_API_KEY — Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key.
DOKPLOY_PROFILES_JSON — Optional JSON object of named Dokploy targets. Use this when you want explicit named profiles in addition to the local default target.

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http vcode-sh-dokploy-mcp https://{remoteHost}{mcpPath}

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "vcode-sh-dokploy-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://{remoteHost}{mcpPath}"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Rodar no PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Abrir

Server facts

Remote

Transport: http
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@vibetools/dokploy-mcp

MCP server for Dokploy that works cleanly with Codex, Cursor, Claude Code, and Claude Desktop.

Three tools up front. Hundreds of Dokploy procedures underneath. Less schema tax, more actual deploys.

Most MCP servers treat your context window like free landfill. This one starts with search, execute, and list_profiles, then earns the rest.

What that buys you:

compact default surface instead of hundreds of raw endpoint tools
generated, broad Dokploy coverage underneath
real workflows for deploys, compose, logs, domains, databases, and profiles
local stdio plus hosted HTTP metadata in the same package

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

Current Fact Snapshot

Generated API procedures in the pinned catalog: 544
Generated tags: 50
Default public MCP tools: 3 (search, execute, list_profiles)
Default tools/list footprint from the current budget check: about 1,681 tokens (6,723 bytes)
Reduction versus the classic endpoint-per-tool baseline (92,354 tokens): 98.2%

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

Quick Start

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

For env-based setup, start from .env.example.

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": "dokp_..."
      }
    }
  }
}

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.

Using multiple Dokploy organizations?

Keep one compact MCP server and configure profiles with DOKPLOY_PROFILES_JSON:

{
  "mcpServers": {
    "dokploy": {
      "command": "npx",
      "args": ["@vibetools/dokploy-mcp"],
      "env": {
        "DOKPLOY_PROFILES_JSON": "{\"redivo\":{\"url\":\"https://redivo.example.com\",\"apiKey\":\"dokp_redivo\"},\"personal\":{\"url\":\"https://personal.example.com\",\"apiKey\":\"dokp_personal\"},\"mezon\":{\"url\":\"https://mezon.example.com\",\"apiKey\":\"dokp_mezon\"}}"
      }
    }
  }
}

Use list_profiles to see the available default and named profile targets without exposing API keys. Pass profile to execute when you want a named profile instead of the default target:

{
  "profile": "redivo",
  "code": "return await dokploy.project.all()"
}

search also accepts an optional profile argument for profile-name validation while preserving the same compact catalog behavior.

Hosted HTTP sessions keep their request-scoped remote credentials bound to the session. Named local profiles are not exposed there.

Want the wizard path instead of manual config?

npx @vibetools/dokploy-mcp setup

Pick Your Client

What You Actually Get

search: discover Dokploy procedures and contracts
execute: run multi-step workflows in one sandboxed call
list_profiles: list configured Dokploy profile names and URLs without secrets
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 trying to outsmart a problem that already has a working shape.

Read These Next

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.

Dokploy

Adicionar este servidor

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Dokploy?

Does Dokploy need an API key?

What transport does Dokploy use?

When was Dokploy last checked?

Documentation

@vibetools/dokploy-mcp

Current Fact Snapshot

Quick Start

Pick Your Client

What You Actually Get

Read These Next

CLI

Development

Credits

License