setuplisted

# mcp-multiplexer setup Set up mcp-multiplexer end to end. Work through the steps in order. Ask the user before destructive steps (config edits) and whenever a choice is genuinely theirs (which servers to migrate, OAuth, governance); otherwise proceed with the defaults given here. ## 1. Install the binary Check first: `mcp-multiplexer --version`. If it runs, note the version and skip to step 2. Otherwise install a prebuilt binary (no sudo): ```sh mkdir -p ~/.local/bin # pick the asset by `uname -s`/`uname -m`: # Linux x86_64 mcp-multiplexer-x86_64-unknown-linux-musl.tar.gz # Linux ARM64 mcp-multiplexer-aarch64-unknown-linux-musl.tar.gz # macOS Intel mcp-multiplexer-x86_64-apple-darwin.tar.gz # macOS ARM mcp-multiplexer-aarch64-apple-darwin.tar.gz # Windows x86_64 mcp-multiplexer-x86_64-pc-windows-msvc.zip curl -L https://github.com/johgirard/mcp-multiplexer/releases/latest/download/<asset> | tar xz -C ~/.local/bin ``` If `~/.local/bin` is not on the user's PATH, tell them how to add it (or use `/usr/local/bin` with sudo). Fallback when cargo is available: `cargo install mcp-multiplexer`. Verify with `mcp-multiplexer --version`. ## 2. Inventory existing MCP servers Read, don't modify yet: - Claude Code user scope: `~/.claude.json` → top-level `mcpServers` - Project scope: `./.mcp.json` → `mcpServers` - If the user mentions other clients: Cursor `~/.cursor/mcp.json`, etc. Present the inventory. Then ask which servers to migrate. Recommendations: