MCP server de Dokploy
✓ VerificadoPermite que los clientes de IA gestionen despliegues, bases de datos, dominios y logs de Dokploy mediante una interfaz compacta y eficiente en el uso de tokens.
También conocido como vcode-sh/dokploy-mcp, dokploy-mcp, @vibetools/dokploy-mcp
- Stars
- 4
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 4.0.0
- Último commit
- 9 jul 2026
- Licencia
- MIT
¿Qué es Dokploy MCP?
Dokploy es un MCP server. Permite que los clientes de IA gestionen despliegues, bases de datos, dominios y logs de Dokploy mediante una interfaz compacta y eficiente en el uso de tokens.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Dokploy
Dokploy MCP ofrece una forma para que clientes de IA como Claude Desktop, Cursor, Codex y Claude Code interactúen con el PaaS de Dokploy. Se enfoca en la eficiencia mediante el uso de una interfaz compacta que reduce significativamente la cantidad de tokens enviados a la ventana de contexto. En lugar de exponer cientos de esquemas de endpoints individuales, utiliza tres herramientas principales: search, execute y list_profiles. Este enfoque permite que el servidor gestione cientos de procedimientos subyacentes manteniendo un consumo mínimo de recursos.
Los usuarios configuran el servidor vía npx utilizando un DOKPLOY_URL y un DOKPLOY_API_KEY obtenidos desde la configuración de Dokploy. El servidor soporta conexiones locales vía stdio y metadatos mediante HTTP alojado. Para desarrolladores que gestionan múltiples organizaciones, la variable de entorno DOKPLOY_PROFILES_JSON permite configurar múltiples perfiles con nombre. Esto permite que la IA cambie entre diferentes instancias de Dokploy al pasar el nombre de un perfil a la herramienta execute, facilitando flujos de trabajo complejos para despliegues, bases de datos, dominios y logs sin exponer credenciales sensibles.
Qué puedes hacer con él
- 1Gestionar múltiples cuentas de DokployIndica a la IA que realice acciones en una organización específica utilizando perfiles con nombre.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Dokploy MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Dokploy MCP en Claude Code
$ 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-mcpInstalar Dokploy MCP en Cursor
~/.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>"
}
}
}
}Instalar Dokploy MCP en VS Code
.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>"
}
}
}
}Instalar Dokploy MCP en VS Code CLI
$ 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>"}}'Instalar Dokploy MCP en Claude Desktop
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>"
}
}
}
}Instalar Dokploy MCP en Codex
$ 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-mcpInstalar Dokploy MCP en Codex config.toml
~/.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>"
Instalar Dokploy MCP en Gemini CLI
$ 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-mcpInstalar Dokploy MCP en Gemini settings.json
~/.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>"
}
}
}
}Configuración
DOKPLOY_API_KEYSecretoOptional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key.
DOKPLOY_PROFILES_JSONSecretoOptional 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.
| Nombre | Descripción | Tipo |
|---|---|---|
| DOKPLOY_API_KEY | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key. | Secreto |
| 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. | Secreto |
| DOKPLOY_URL | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL. |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblevcode-sh/dokploy-mcp is public and reachablegithub.com/vcode-sh/dokploy-mcp ↗Aprobado
- El paquete indica este repositorio como su origen@vibetools/dokploy-mcp names vcode-sh/dokploy-mcp as sourcenpmjs.com/package/@vibetools/dokploy-mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for @vibetools/dokploy-mcpnpmjs.com/package/@vibetools/dokploy-mcp/v/4.0.0#provenance ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-07-09github.com/vcode-sh/dokploy-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @vibetools/dokploy-mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependencias105 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPEndpoint did not answer initialize: unreachableHallazgo
README
Ver en GitHub@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.
Preguntas sobre Dokploy MCP
¿Cómo agrego Dokploy MCP a Claude Code?
Ejecuta 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 en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Dokploy MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Dónde puedo encontrar mi API key?
Tu API key se encuentra en tu dashboard de Dokploy en Settings > Profile > API/CLI.
¿Puedo gestionar múltiples organizaciones de Dokploy?
Sí, puedes configurar múltiples perfiles usando la variable de entorno DOKPLOY_PROFILES_JSON para alternar entre diferentes objetivos.
¿Qué herramientas están disponibles por defecto?
El servidor proporciona tres herramientas públicas por defecto: search, execute y list_profiles.