inspector

This draft PR introduces a shared code architecture that enables code reuse across the MCP Inspector's CLI, TUI, and web client interfaces. This addresses the feature drift and maintenance burden caused by the CLI and web client maintaining separate implementations, with immediate code sharing across the CLI and TUI, and planned support for the web client (v2). What's Included 1. TUI Integration Integrated the TUI from as a first-class workspace TUI is accessible via flag Currently experimental; feature gaps include OAuth, completions, elicitation, and sampling 2. Shared Package () Created internal workspace package for shared MCP client code Includes - a comprehensive wrapper around the MCP SDK that manages: Client and transport lifecycle Message tracking and stderr logging Server data management (tools, resources, prompts) Event-driven updates via (cross-platform compatible) High-level MCP method wrappers with automatic parameter conversion 3. CLI Migration Migrated CLI to use from shared package Consolidated CLI helper functions into methods Removed duplicate code (CLI transport implementation, directory, etc) All CLI tests passing 4. Shared React Code hook for reactive state management Works in both TUI and v2 web client (future) Subscribes to events and provides reactive React state Architecture The shared package includes: MCP client/server interaction (, transport creation, config loading) Shared React code (hooks, components, etc.) JSON utilities for parameter conversion Test fixtures and harness servers Both CLI and TUI now use the same implementation, ensuring consistent behavior and eliminating code duplication (both apps are now thin UX-only implementations). Next Steps Phase 4: TUI Feature Gap Implementation (Planned) Address TUI feature gaps (OAuth, completions, elicitation, sampling) by extending This dual-purpose approach: brings TUI to feature parity while preparing for v2 web client integration When complete, will be very close to ready for full v2 web client support Phase 5: v2 Web Client Integration (Planned) Integrate with the v2 web client once Phase 4 is complete and v2 web client is ready Update and other shared code as required to support v2 while maintaining CLI and TUI compatability Documentation See (included in this PR) for: Complete architecture overview capabilities and API Integration history and current usage patterns Detailed web client integration plan Testing All CLI tests passing TUI tested with test harness servers TypeScript Project References ensure correct build ordering CI workflow updated to build shared package first This is a draft PR for review. Feedback welcome on the architecture and integration approach.