This container is a deliberately empty placeholder. The real MCP server — exposing your DeployLane account state and scaffolders to AI agents — lands in a follow-up release.
The point of this build is to prove DeployLane can deploy a
multi-container app via its own self-update flow. You're seeing
this page because mcp.deploylane.dev routes to a
second container in the DeployLane compose stack.