Access Dokploy's full API through one MCP proxy with lower token usage.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-dokploy-fullapi-proxy" yet — see the docs or source repo.
Use mcp-dokploy-fullapi-proxy to connect to my configured Dokploy instances and list the available projects or service resources in each one.
A Dokploy resource overview grouped by instance for unified multi-environment visibility.
Use this MCP proxy to access Dokploy's full API, show the available interface scope, and choose the needed endpoints to complete my task.
An explanation that the proxy exposes Dokploy's full tRPC API and uses the relevant endpoints for the task.
When handling Dokploy management tasks, prefer on-demand skill loading to minimize context and token usage, and explain where it saves tokens versus the official MCP.
The task is completed with on-demand loading, along with a note on token-saving advantages over the official MCP.
DevOps engineers or developers maintaining multiple Dokploy instances can use this MCP proxy as a single access point. It reduces switching overhead and centralizes API operations.
When a team wants an AI assistant to perform broader Dokploy management tasks, this tool exposes Dokploy's full tRPC API. It is better suited for wider automation coverage than a limited interface set.
If token cost is a concern in MCP-driven operations, this proxy's on-demand skill loading is useful. It claims significant token savings compared with the official MCP.
It is a single-tool MCP proxy that exposes Dokploy's full tRPC API. The description says it covers 473 endpoints and supports multi-instance access.
The provided description says it reduces token usage through a single-tool design and on-demand skill loading. It claims about 77% to 92% token savings versus the official MCP.
The available material does not provide installation steps, runtime requirements, or key configuration details. See the source repository for specifics.
Manage Dokploy projects, apps, databases, and deployments through MCP tools.
Manage Dokploy apps, databases, domains, backups, and servers from one interface.
Proxy multiple MCP servers while reducing token usage with on-demand tool loading.
Connect Dokploy to Codex, Cursor, and Claude through an MCP server.
Aggregate, filter, transform, and compose MCP tools through one proxy.
Securely proxy MCP services as OpenAPI endpoints for easier integration and deployment.