edpaserverlisted

# EDPA Server — Local PI Planning UI > **Experimental in V2.0.** The PI planning server is a *complement* to > the canonical CLI/skill workflow, not a replacement. Per ADR-009 the > default install does not vendor the server (~50 MB Node payload). Opt > in with `./install.sh --with-server`. ## What this does Starts a long-lived Node process at `localhost:3001`. The process: - Serves the React SPA from `.claude/edpa/server/dist/` (frontend build). - Exposes HTTP endpoints under `/api/*` that translate to MCP `tools/call` against the bundled `mcp_server.py`. Every read/write goes through MCP — the UI never touches YAML directly. - Keeps one long-lived MCP subprocess across requests (per ADR open question in concept.md: long-lived > spawn-per-request). - Writes its PID to `.edpa/.server.pid` (gitignored). Each developer runs their own local instance — there is no shared server in V2.0. Multi-user planning happens via `git pull` between sessions. ## Arguments `$ARGUMENTS` — one of: - `start` — spawn the Node process, write PID file. No-op if already running. - `stop` — kill the running PID, remove PID file. No-op if not running. - `status` — print PID, port, uptime. Exit 1 if not running. - `restart` — `stop` then `start`. ## Steps ### 1. Verify the server is installed The server bundle lives at `.claude/edpa/server/`. If missing: ``` ERROR: PI planning server not installed. Re-run: ./install.sh --with-server ``` ### 2. Run the subcommand ```bash # star