No user-submitted related servers found.
Scored across 463 tools
Many tools are clearly distinct by resource type (e.g., mysql, postgres, redis each have their own lifecycle tools), but there is significant overlap among actions like start, stop, deploy, redeploy, reload, rebuild, and changeStatus which may confuse agents. Also, multiple tools named 'all' or 'getAll' across different resources could be ambiguous without clear resource context.
Tool names follow a consistent pattern: resource name (e.g., application, mysql) followed by an action (e.g., create, update, delete). However, there are minor inconsistencies like 'all' vs 'allForPermissions' and some tools use different verb styles (e.g., 'get' vs 'one', 'create' vs 'register'). Overall, the pattern is predictable.
With 463 tools, the count is far beyond any reasonable scope for an MCP server. The server appears to expose the entire API surface of Dokploy, including many internal or rarely used endpoints. This makes it extremely heavy and impractical for an agent to navigate.
The tool surface is extensive, covering CRUD for most resources, deployments, backups, notifications, and settings. However, there are gaps like missing update for some providers (e.g., github update is present but no corresponding get for individual provider data), and some lifecycle actions are inconsistent across resource types (e.g., mysql has changeStatus but mongo does not). The completeness is high but not perfectly uniform.