Dokploy MCP server
✓ VerifiziertErmöglicht es AI-Clients, Dokploy-Deployments, Datenbanken, Domains und Logs über eine kompakte, token-effiziente Schnittstelle zu verwalten.
Auch bekannt als vcode-sh/dokploy-mcp, dokploy-mcp, @vibetools/dokploy-mcp
- Stars
- 4
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 4.0.0
- Letzter Commit
- 9. Juli 2026
- Lizenz
- MIT
Was ist Dokploy MCP?
Dokploy ist ein MCP server. Ermöglicht es AI-Clients, Dokploy-Deployments, Datenbanken, Domains und Logs über eine kompakte, token-effiziente Schnittstelle zu verwalten.
Zusammenfassung generiert aus dem README des Projekts
Über Dokploy MCP server
Dokploy MCP bietet AI-Clients wie Claude Desktop, Cursor, Codex und Claude Code eine Möglichkeit, mit dem Dokploy PaaS zu interagieren. Der Fokus liegt auf Effizienz: Durch eine kompakte Schnittstelle wird die Anzahl der Tokens, die an das Context Window gesendet werden, deutlich reduziert. Anstatt hunderte einzelne Endpoint-Schemas offenzulegen, nutzt der Server drei primäre Tools: search, execute und list_profiles. Dieser Ansatz erlaubt es dem Server, hunderte zugrunde liegende Prozeduren zu verwalten und dabei einen geringen Footprint beizubehalten.
Nutzer richten den Server via npx unter Verwendung einer DOKPLOY_URL und eines DOKPLOY_API_KEY ein, den du in den Dokploy-Einstellungen findest. Der Server unterstützt lokale stdio-Verbindungen und hosted HTTP-Metadaten. Für Entwickler, die mehrere Organisationen verwalten, ermöglicht die Umgebungsvariable DOKPLOY_PROFILES_JSON die Konfiguration mehrerer benannter Profile. Dies erlaubt es der KI, zwischen verschiedenen Dokploy-Instanzen zu wechseln, indem einfach der Profilname an das execute-Tool übergeben wird. So lassen sich komplexe Workflows für Deployments, Datenbanken, Domains und Logs steuern, ohne sensible Credentials preiszugeben.
Was du damit machen kannst
- 1Mehrere Dokploy-Accounts verwaltenSteuere die KI an, um Aktionen in einer spezifischen Organisation mithilfe benannter Profile durchzuführen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Dokploy MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenDokploy MCP in Claude Code installieren
$ claude mcp add --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp -- npx -y @vibetools/dokploy-mcpDokploy MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Dokploy MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"dokploy-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Dokploy MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"dokploy-mcp","type":"stdio","command":"npx","args":["-y","@vibetools/dokploy-mcp"],"env":{"DOKPLOY_API_KEY":"<YOUR_DOKPLOY_API_KEY>","DOKPLOY_PROFILES_JSON":"<YOUR_DOKPLOY_PROFILES_JSON>"}}'Dokploy MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Dokploy MCP in Codex installieren
$ codex mcp add dokploy-mcp --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' -- npx -y @vibetools/dokploy-mcpDokploy MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.dokploy-mcp] command = "npx" args = ["-y", "@vibetools/dokploy-mcp"] [mcp_servers.dokploy-mcp.env] DOKPLOY_API_KEY = "<YOUR_DOKPLOY_API_KEY>" DOKPLOY_PROFILES_JSON = "<YOUR_DOKPLOY_PROFILES_JSON>"
Dokploy MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' -e 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp npx -- -y @vibetools/dokploy-mcpDokploy MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Konfiguration
DOKPLOY_API_KEYSecretOptional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key.
DOKPLOY_PROFILES_JSONSecretOptional JSON object of named Dokploy targets. Use this when you want explicit named profiles in addition to the local default target.
DOKPLOY_URLOptional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL.
| Name | Beschreibung | Typ |
|---|---|---|
| DOKPLOY_API_KEY | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key. | Secret |
| 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. | Secret |
| DOKPLOY_URL | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL. |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarvcode-sh/dokploy-mcp is public and reachablegithub.com/vcode-sh/dokploy-mcp ↗Bestanden
- Paket nennt dieses Repository als Quelle@vibetools/dokploy-mcp names vcode-sh/dokploy-mcp as sourcenpmjs.com/package/@vibetools/dokploy-mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for @vibetools/dokploy-mcpnpmjs.com/package/@vibetools/dokploy-mcp/v/4.0.0#provenance ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-07-09github.com/vcode-sh/dokploy-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @vibetools/dokploy-mcpBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten105 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeEndpoint did not answer initialize: unreachableBefund
README
Auf GitHub ansehen@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
stdioplus 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/listfootprint from the current budget check: about1,681tokens (6,723bytes) - Reduction versus the classic endpoint-per-tool baseline (
92,354tokens):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 contractsexecute: run multi-step workflows in one sandboxed calllist_profiles: list configured Dokploy profile names and URLs without secrets- optional
rawmode: one tool per procedure - optional
hybridmode: Code Mode plus selected raw tools - optional hosted HTTP path with
server.jsonmetadata 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
- docs/getting-started.md
- docs/guides/profiles.md
- docs/guides/modes.md
- docs/guides/compose.md
- docs/guides/hosted-http.md
- docs/guides/hosted-deploy.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.
Dokploy MCP Fragen
Wie füge ich Dokploy MCP zu Claude Code hinzu?
Führe claude mcp add --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp -- npx -y @vibetools/dokploy-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Dokploy MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wo finde ich meinen API-Key?
Dein API-Key befindet sich in deinem Dokploy-Dashboard unter Settings > Profile > API/CLI.
Kann ich mehrere Dokploy-Organisationen verwalten?
Ja, du kannst mehrere Profile über die Umgebungsvariable DOKPLOY_PROFILES_JSON konfigurieren, um zwischen verschiedenen Targets zu wechseln.
Welche Tools sind standardmäßig verfügbar?
Der Server stellt drei öffentliche Standard-Tools bereit: search, execute und list_profiles.