Best for
- Teams already operating Dokploy and needing API automation
- Developers who want centralized Dokploy resource management in an MCP client
D
44FMRS · D
The source identifies this as Dokploy's official MCP package, supporting stdio, Streamable HTTP, and legacy SSE transports with API-token authentication. Because the server manifest was not cached and the source does not list concrete tool identifiers, no tool identifiers are included.
The official Dokploy MCP package exposes Dokploy API endpoints as tools for MCP-compatible clients. The README states that it provides 508 tools across 49 categories, covering projects, applications, Compose, databases, servers, Docker, clusters, security, backups, notifications, Git providers, billing, and other Dokploy functions.
Tools
The tool list has not been reviewed yet.
Setup
Use Node.js 18 or later and have a running Dokploy server. Add the supplied JSON configuration to an MCP client and set DOKPLOY_URL and DOKPLOY_API_KEY. Bun, Deno, Docker, and HTTP-mode deployments are also documented.
claude_desktop_config.json
{"mcpServers":{"dokploy-mcp":{"command":"npx","args":["-y","@dokploy/mcp"],"env":{"DOKPLOY_URL":"https://your-dokploy-server.com","DOKPLOY_API_KEY":"your-dokploy-api-token"}}}}
Fit and risk
Not for
- Users without a Dokploy server or API token
- Use cases requiring management of platforms other than Dokploy without a corresponding API
Required permissions
- Access to the Dokploy server URL is required
- A Dokploy API authentication token is required
- Depending on the API operation, the server may have permission to create, modify, deploy, stop, delete, and manage security-sensitive resources
Risks and side effects
- The server exposes a broad range of Dokploy API operations, including potentially destructive deployment, stop, deletion, password, and security actions
- API responses may contain environment variables, tokens, passwords, or other sensitive fields; set DOKPLOY_REDACT_ENV=true to redact them
- Protect DOKPLOY_API_KEY and any service tokens supplied through DOKPLOY_CUSTOM_HEADERS
Troubleshooting
- Confirm that Node.js is version 18 or later
- Verify DOKPLOY_URL and DOKPLOY_API_KEY and ensure the Dokploy server is running
- Use DOKPLOY_ENABLED_TAGS to filter categories if too many tools load
- Check timeout and retry environment variables
- Try @latest and use MCP Inspector when connection diagnosis is needed
Use cases
Manage Dokploy project and application lifecycles through an AI client
Operate databases, backups, domains, notifications, and infrastructure settings
Connect Dokploy to MCP clients over stdio or HTTP
Supported clients
CursorFull support
WindsurfFull support
VS CodeFull support
Claude CodeFull support
ZedFull support
Claude DesktopFull support
BoltAIFull support