mirror of
https://github.com/lWolvesl/claw-code.git
synced 2026-04-02 07:41:52 +08:00
Add a minimal runtime MCP client bootstrap layer that turns typed MCP configs into concrete transport targets with normalized names, tool prefixes, signatures, and auth requirements. This is intentionally scaffolding rather than a live connection manager: it creates the real data model the runtime will need to launch stdio, remote, websocket, sdk, and claude.ai proxy clients without prematurely coupling the code to any specific async transport implementation. Constraint: Keep the slice real and minimal without adding connection lifecycle complexity yet Constraint: Runtime verification must stay green under fmt, clippy, and tests Rejected: Implement live connection/session orchestration in the same commit | too much surface area for a clean foundational slice Rejected: Leave bootstrap shaping implicit in future transport code | would duplicate transport mapping and weaken testability Confidence: high Scope-risk: narrow Reversibility: clean Directive: Build future MCP launch/execution code by consuming McpClientBootstrap/McpClientTransport rather than re-parsing config enums ad hoc Tested: cargo fmt --all; cargo clippy -p runtime --all-targets -- -D warnings; cargo test -p runtime Not-tested: live MCP server processes; remote stream handshakes; tool/resource enumeration against real servers