MCP App Dev Setup

Bootstraps the development loop documented in docs/development-with-forge.md. The user is an L6/L7 engineer who knows their way around but hasn't worked with Forge before. Bias toward doing the work and reporting back, not asking each step.

What you set up

The dev loop has four pieces, all of which must be working:

1. Forge clone at ../forge/ (sibling of elastic-o11y-mcp/)
2. Forge Python venv with the package installed in editable mode (pip install -e ".[dev]")
3. MCP App build — npm install && npm run build in elastic-o11y-mcp/
4. Cluster access — oteldemo-esyox GKE cluster credentials in .env, validated by a Forge live status check

If any piece is missing or broken, repair it. If the user has a clear preference (different cluster, different repo location), defer to it.

Sequence

Step 1 — Locate or clone Forge