start

Starts the LiteLLM proxy, Docker MCP services, and local Python MCP servers in dependency order.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill start-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/Wizarck/nexandro/tree/main/skills/start
Command: npx skills add https://github.com/Wizarck/nexandro --skill start-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a local MCP server stack with Docker?▼

Run the /start command, which launches the LiteLLM proxy first, then brings up the Docker compose stack with docker compose up -d, and finally starts the host-based Python MCP servers. Each service is health-checked via curl before and after startup.

Why must LiteLLM start before Docker services?▼

Hindsight calls the LiteLLM proxy during its verify_connection step at container startup. If LiteLLM is not reachable on port 4000, the Hindsight container fails to initialize, so the Skill enforces this start order.

What happens if Docker Desktop is not running?▼

The Skill detects the failure via docker info, launches Docker Desktop automatically, and polls for up to 60 seconds. If the daemon does not respond in time, it prints an error asking you to open Docker Desktop manually and rerun /start.

Does the start command fail if services are already running?▼

No. The Skill probes each endpoint first and skips any service that already responds, making the command idempotent. If the whole stack is active, it simply prints the status summary and stops.

How are API keys and secrets loaded for the MCP stack?▼

Secrets are stored in a sops-encrypted secrets.env file in OneDrive and decrypted at startup using an age key. The decrypted variables are exported into the shell environment before any service is launched.