Summary
The Dokploy MCP Server is missing critical compose management tools that exist in the Dokploy REST API but are not exposed via MCP.
Current Situation
Dokploy REST API provides:
compose.update - Update compose configuration including composeFile
compose.deploy - Trigger deployment
compose.one - Get compose details
compose.start / compose.stop - Control compose lifecycle
Dokploy MCP Server exposes:
- ✅
project-* - Project management
- ✅
domain-* - Domain management
- ✅
application-* - Application management
- ✅
postgres-* - PostgreSQL management
- ✅
mysql-* - MySQL management
- ❌ No compose management tools
Requested Tools
| Tool |
Description |
compose-one |
Get compose service details by ID |
compose-update |
Update composeFile, name, description, env |
compose-deploy |
Trigger deployment |
compose-redeploy |
Redeploy service |
compose-start / compose-stop |
Control lifecycle |
Use Case
As a user automating infrastructure with AI assistants (Claude, GitHub Copilot, etc.), I need to:
- Update docker-compose.yml remotely
- Trigger deployments
- Manage compose lifecycle
Without these tools, I must manually copy/paste compose files in the Dokploy UI or write custom API scripts.
Implementation Notes
The REST API endpoints are already functional. This enhancement only requires adding MCP tool definitions that call existing endpoints.
Priority
High - Compose is one of the most common deployment methods, yet has zero MCP support.
Summary
The Dokploy MCP Server is missing critical
composemanagement tools that exist in the Dokploy REST API but are not exposed via MCP.Current Situation
Dokploy REST API provides:
compose.update- Update compose configuration includingcomposeFilecompose.deploy- Trigger deploymentcompose.one- Get compose detailscompose.start/compose.stop- Control compose lifecycleDokploy MCP Server exposes:
project-*- Project managementdomain-*- Domain managementapplication-*- Application managementpostgres-*- PostgreSQL managementmysql-*- MySQL managementRequested Tools
compose-onecompose-updatecompose-deploycompose-redeploycompose-start/compose-stopUse Case
As a user automating infrastructure with AI assistants (Claude, GitHub Copilot, etc.), I need to:
Without these tools, I must manually copy/paste compose files in the Dokploy UI or write custom API scripts.
Implementation Notes
The REST API endpoints are already functional. This enhancement only requires adding MCP tool definitions that call existing endpoints.
Priority
High - Compose is one of the most common deployment methods, yet has zero MCP support.