Inspector V2 Working Group Meeting - May 27, 2026

Agenda

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

Attendees

• Cliff Hall
• Bob Dickinson
• Thierry Damiba

Discussion

Cliff Hall demonstrated new V2 debugging surfaces, including a network tab that tracks HTTP traffic and OAuth flows. Bob Dickinson cautioned that OAuth state across redirects needs careful handling — earlier implementations stashed in-flight messages to avoid losing session continuity.

Messages and history. The group discussed renaming the "Logs" tab to "Messages" so it covers both requests and unsolicited server notifications, unifying HTTP and server-originated messages into a single filterable list keyed by an origin field. Rather than storing raw streaming payloads, they favored correlating requests with their resulting messages via trace IDs / links so users can jump between network history and the message log. Cliff proposed formatting logs, HTTP, and protocol data with OpenTelemetry to enable drill-downs and timeline views.

Export and replay. The team explored JSON export of logs and history as a shareable "crash dump" for collaborative debugging, plus the ability to pin and replay specific requests or notifications (with annotations) without re-running a whole flow.

Secrets and OAuth. They adopted a URI-based secret-injection convention (e.g. env:, onepassword:) inspired by Microsoft's approach to support arbitrary secret stores, noting keystore storage limits portability. For client identity, a SIMD URI can live in the client-ID field; whether to ship a default SIMD implementation was left open.

Configuration and forms. Cliff suggested roots may be better configured per-server than globally. The team wants to import server configs from the registry / command line so authors can validate server JSON in the Inspector before publishing — with command-line server definitions treated as ephemeral. Bob and Cliff also identified the need for a single consolidated module to render forms from JSON schema, replacing today's fragmented tool-parameter and server-config implementations.

Next Steps

• Cliff Hall: Verify OAuth state stash / re-injection after navigation; add a client-vs-server origin indicator to the messages panel; file issues for registry import and history origin; research OpenTelemetry log formatting; use Claude to analyze existing forms before consolidating.
• Bob Dickinson: Implement registry support and server-card configuration.
• Thierry Damiba: Evaluate the V1 repo for active issues and post a status summary.
• The group: Choose a registry mirror; research CLI/TUI touchpoints for the V2 migration.

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