Inspector V2 Working Group Meeting - Jun 3, 2026

Agenda

• Discuss progress toward feature completeness for a release candidate
• Items on the V2 board and planning

Attendees

• Cliff Hall
• Ola Hungerford
• Enrico Toniato

Discussion

Cliff Hall reported substantial progress porting the Inspector core from V1.5 to V2 — "four or five PRs to get it properly right" — with the core now functional and HTTP logs added. He demonstrated the apps interface using a "Nightrider" MCP server; Ola Hungerford noted she had built similar drum-related tooling previously.

UX improvements. Progress is now surfaced via toast notifications so users aren't penalized for navigating away during long operations; search filters and scroll positions persist across tab switches; a newest-first / oldest-first toggle replaces complex autoscroll logic; and connection info shows client capabilities only when a connection is active.

OAuth debugging. The team settled on server-side network filtering rather than client-side complexity, eliminating the "app-within-an-app" structure and CORS issues from earlier attempts — all needed debugging information comes through the network logs.

Schema and elicitation. The Inspector already warns on output/schema mismatches; polymorphic tool responses need more explicit handling. Elicitation enums are in place (including legacy formats), though Cliff and Ola observed that protocol changes don't dictate how LLM APIs ultimately handle those values.

Multi-server and versioning. Infrastructure for multiple concurrent connections exists but only one is active at a time today; Bob has a working multi-server TUI, while practical use cases remain uncertain. The team decided to stop maintaining parallel codebases in favor of npm versioning and Git tags. There was strong consensus to freeze V1 development except critical security fixes, target a working V2 by end of Q2, and replace V1 with V2 as soon as possible.

Next Steps

• Cliff Hall: Port the TUI and CLI onto the V2 architecture; auto-clear toast notifications on disconnect; contact Konstantin about the everything-server upgrade timeline (V2 TypeScript SDK now vs. waiting for the new spec).
• Ola Hungerford: Bring the V2 transition plan to the core-maintainer agenda for formal approval; coordinate spec location / July implementation in the maintainer channel.
• The group: Write V2 documentation covering the major changes from V1; invite Konstantin to the next meeting; consolidate or clarify legacy/quick-start repos so contributors don't invest in deprecated work.

Transcript

• Gemini Meeting Transcript / Summary

Operational Details

• Our Charter
• Weekly Working Group Meeting takes place Wednesdays 11am EST on Google Meet
• Agenda / Meeting Notes are published on GitHub Discussions
• We are planning on an Inspector V2 kanban board in GitHub Project
• We are building on a v2/main branch of the Inspector repo
• We are experimenting on a v1.5/main branch of the Inspector repo
• View the Open pull requests labeled as V2
• View the Open issues labeled as V2