Skip to main content

​
Group Type

Working Group

​
Mission Statement

The Inspector V2 Working Group is building Inspector V2, a new web-based MCP inspector redesigned from the ground up for maintainability and reliability. The group delivers a shared Inspector Core architecture that maximizes code reuse across Web, CLI, and TUI implementations, together with a comprehensive testing apparatus. This effort requires cross-maintainer collaboration because it spans UI, protocol tooling, and test infrastructure that no single maintainer owns today.

​
Scope

​
In Scope

  • The modelcontextprotocol/inspector repository, including:
  • Inspector Core — a new shared-code architecture that provides common MCP and protocol interfaces for all Inspector front-ends.
  • Web Inspector UI — browser-based inspector built on Mantine and TypeScript.
  • CLI Inspector — command-line interface sharing Inspector Core.
  • TUI Inspector — terminal UI sharing Inspector Core.
  • Testing apparatus — shared test harnesses, fixtures, and integration tests across all Inspector surfaces.
  • Deprecation and migration of the existing Inspector on main to a v1.x maintenance branch.
  • Adoption of MCP TypeScript SDK V2 inside Inspector Core once available.

​
Out of Scope

  • The core MCP specification.
  • MCP SDK maintenance (TypeScript, Python, or any other language SDK).
  • MCP server implementations.
  • SDK WG — Inspector Core consumes the TypeScript SDK; coordination required for SDK V2 adoption.
  • MCP Apps WG — shared surface area around client/app ergonomics and inspection workflows.
  • Auth WG — authentication flows exercised by Inspector when connecting to protected servers.
  • Registry WG — discovery and metadata surfaces that Inspector presents to users.

​
Leadership

RoleNameOrganizationGitHubTerm
WG LeadCliff HallFuturescale@cliffhallOngoing
WG LeadOla HungerfordNordstrom@olaservoOngoing
WG LeadBob DickinsonTeamSpark.ai@BobDickinsonOngoing

​
Authority & Decision Rights

Decision TypeAuthority Level
Meeting logistics & schedulingWG Leads (autonomous)
Proposal prioritization within WGWG Leads (autonomous)
SEP triage & closure (in scope)WG Leads (autonomous, with documented rationale)
Technical design within scopeWG consensus
Spec changes (additive)WG consensus → Core Maintainer approval
Spec changes (breaking/fundamental)WG consensus → Core Maintainer approval + wider review
Scope expansionCore Maintainer approval required
WG Member approvalWG Member sponsors

​
Membership

NameOrganizationGitHubDiscordLevel
Cliff HallFuturescale@cliffhallseaofarrowsMaintainer
Ola HungerfordNordstrom@olaservoolaservoMaintainer
Bob DickinsonTeamSpark.ai@BobDickinsonrddthreeMaintainer
Tobin SouthAnthropic@tobinsouthtobinsouthMember

​
Operations

MeetingFrequencyDurationPurpose
Working SessionWeekly, Wednesdays 11:00 America/New_York60 minutesTechnical discussion, proposal review
Meetings are held at meet.modelcontextprotocol.io/tag/inspector-v2-wg. Agendas are posted at least 7 days in advance per current MCP meeting policy. Meeting notes are published to the Meeting Notes — Inspector V2 WG discussion category in the modelcontextprotocol/modelcontextprotocol repository. Communication channels
  • Primary channel: #inspector-v2-wg on the MCP Discord.
  • Async discussion: GitHub Discussions in modelcontextprotocol/inspector.
  • Quarterly updates: posted to the WG’s GitHub Discussions category.

​
Deliverables & Success Metrics

​
Active Work Items

Work ItemStatusOwner(s)
Web Inspector UI (Mantine / TypeScript) — dumb components with real MCP/Core interfacesIn ProgressCliff Hall, Ola Hungerford
Inspector Core shared-code architectureIn ProgressBob Dickinson
CLI Inspector and TUI InspectorIn ProgressBob Dickinson
Migration of existing Inspector on main to v1.x maintenance branchPlanningWG Leads
Testing apparatus across Core, Web, CLI, and TUIPlanningWG Leads
Inspector Core adoption of MCP TypeScript SDK V2Blocked (gated by TS SDK WG)Bob Dickinson

​
Success Criteria

  1. End of Q1 — Web UI complete with “dumb” components wired to real MCP/Inspector Core interfaces.
  2. End of Q1 — Inspector Core architecture finalized.
  3. End of Q2 — Inspector Core merged to v2/main and working end-to-end with the Web UI.
  4. End of Q2 — CLI and TUI Inspectors merged to v2/main and working end-to-end with Inspector Core.
  5. End of Q2 — Existing Inspector on main moved to the v1.x branch and officially deprecated.
  6. End of Q2 — New Inspector family (Web, CLI, TUI) published and generally available.
  7. End of Q3 — Inspector Core running on MCP TypeScript SDK V2 (gated by the TypeScript SDK WG’s delivery schedule).

​
Changelog

DateChangeAuthor
2026-04-11Initial charter adopted for SEP-2149 compliance.Cliff Hall (Co-Lead)