modelcontextprotocol/inspector
Watch
1
0
Fork
You've already forked inspector
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
inspector/specification
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
olaservo ce39e0de7c spec: Add v2 storage specification proposing Zustand 
Closes #983

Proposes a hybrid state management architecture:
- Zustand for UI preferences, logs display, playground state, testing profiles
- Keep useReducer + Context for connection/execution state machines
- Repository interfaces remain storage-agnostic for proxy API integration

Includes detailed analysis of storage options (Zustand, Redux, Jotai,
Context+useReducer, TanStack Query, Valtio) with pros/cons comparison.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-19 07:17:38 -07:00
..
screenshots Remove dark mode screenshots 2025-12-18 05:08:20 -07:00
README.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00
v1_problems.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00
v2_scope.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00
v2_screenshots.md Remove dark mode screenshots 2025-12-18 05:08:20 -07:00
v2_storage.md spec: Add v2 storage specification proposing Zustand 2026-01-19 07:17:38 -07:00
v2_tech_stack.md Update components to use Mantine with rationale 2025-12-18 05:04:50 -07:00
v2_ux.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00
v2_ux_features.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00
v2_ux_handlers.md docs(spec): Restructure UX docs and add visual reference 2025-12-17 09:06:08 -07:00

README.md

Inspector V2 Brief

Brief | V1 Problems | V2 Scope | V2 Tech Stack

UX: Overview | Features | Handlers | Screenshots

Table of Contents

Motivation and Context

The existing Inspector is hard to maintain for a number of reasons. We decided to create a more maintainable Inspector from the ground up, that retains the deterministic boundary of operation, but exposes a plugin architecture.

Track Protocol Conformance

  • Identify any gaps in V1 inspector
  • Track which features are covered
  • Implement to parity and fill gaps
  • Provide conformance testing in CI

Improve Maintainability

  • Clearer separation of concerns
  • Smaller, reusable components

Provide Extensibility

  • Plugin SDK / API
  • Third parties cand develop/maintain their own plugins for features such as
    • LLM usage
    • Evals
    • Multiple server connections
    • Apps playground
    • Testing of registry configuration
    • Interface with registry

Proper Documentation

  • One big README won't cut it anymore
  • Published documentation in MDX should
    • Render in style of spec
    • Kept up to date
    • Cover all features
    • Discuss troubleshooting strategies
    • Provide detailed contribution guidance that explains architecture and expected idioms