What problem does it solve? Manually launching a multi-service MCP stack (LiteLLM proxy, Docker containers, Python MCP servers) is error-prone because services have startup dependencies, such as Hindsight requiring LiteLLM to be reachable at boot. This Skill automates the full startup sequence with health checks and fallback path resolution. ## Core Features & Use Cases - Ordered stack startup: Launches LiteLLM first, then the Docker compose stack (Hindsight, Atlassian, Google Workspace servers), then host-based Python servers (skills-manager, paperclip-mcp, notebooklm). - Idempotent health checks: Probes each service endpoint before starting it, skipping anything already running and printing a consolidated status report. - Secrets and path resolution: Decrypts a sops-encrypted secrets.env file and resolves OneDrive/ELIGIA_DIR paths from a device config with fallbacks. - Use Case: At the beginning of a work session, run /start to bring up the entire MCP toolchain and get a port-by-port status summary instead of launching six services by hand. ## Quick Start Run the /start command to launch the full MCP stack and print the status of every service.