-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Description
Summary
The MCP server currently lacks endpoints for retrieving logs, which limits LLM agents' ability to debug and monitor applications effectively.
Problem
When using the Dokploy MCP with an LLM agent, there's no way to:
- View deployment/build logs
- View runtime container logs
- Debug failed deployments or application errors
The agent can start, stop, deploy, and configure applications but cannot see what's happening inside them. This makes troubleshooting impossible without manual intervention via the web UI or SSH.
Requested Features
1. Deployment Logs
deployment-logs
- deploymentId: string (required)
- tail?: number (optional, limit lines)
Returns build/deployment output for a specific deployment.
2. Container Runtime Logs
application-logs
- applicationId: string (required)
- tail?: number (optional, limit lines)
- since?: string (optional, e.g., "1h", "30m")
Returns live container logs (equivalent to docker logs).
3. Compose Service Logs
compose-logs
- composeId: string (required)
- serviceName?: string (optional, specific service)
- tail?: number
- since?: string
Use Case
As an LLM agent, I need to:
- Deploy an application
- Check if deployment succeeded by reading build logs
- Monitor runtime logs for errors
- Help users debug issues without them needing to leave their terminal
Additional Context
Dokploy's API already supports log retrieval - this is just about exposing those endpoints through the MCP server.
Metadata
Metadata
Assignees
Labels
No labels