Inspector V2 Working Group Meeting - July 1, 2026

Agenda

• Items on the V2 board and planning
• Update on Contributors.md
• Update on the V2 SDK (from Konstantin)
• Discuss progress toward readiness for a release candidate.

Attendees

• Cliff Hall
• Bob Dickinson
• Konstantin Konstantinov

Discussion

This week's session centered on Konstantin's briefing on the V2 TypeScript SDK, whose beta shipped the same day (July 1). The through-line for the Inspector: the SDK's protocol strategy, migration tooling, and testing model all directly shape what V2 needs to support at release.

V2 SDK beta shipped; final targeted for July 28. The beta went out July 1, with the stable release slated for July 28 once the top dependents have been migrated; a post-release phase then picks up the stateless-protocol implementation and the follow-on Inspector refactoring. The near-term goal is getting the beta into real hands — the V2 Inspector included — and surfacing blockers early.

Dual-protocol support via client-side routing. The V2 SDK detects server capabilities automatically and falls back to the legacy protocol when needed, so the ecosystem can upgrade without a forced cutover. That mirrors the protocol-detection approach the group already settled on for the Inspector — attempt the new protocol first, fall back to V1 without user configuration — and keeps old and new clients/servers interoperable.

Code mods for migration. Konstantin demoed automated code mods that handle the syntax-level parts of moving to the V2 SDK, targeting high-traffic dependents like Mastra and Firebase so they can be migrated by release day. Bob Dickinson will run the code mod against real code within days to flush out any missing exports or hooks the tool doesn't yet cover, before the final release locks.

Testing infrastructure. The SDK will ship integration-test matrices covering the old/new client × old/new server permutations to guarantee interoperability. Examples are being promoted to "first-class citizens" with mandatory integration tests, and Konstantin will supply integration-test examples the Inspector can lean on.

Servers-repo clean slate. The team plans to stand up a v2/main branch in the servers repository, seeded from the current main, and eventually replace main outright — a clean-slate refactor to shed accumulated technical debt rather than carry it forward. Cliff Hall will initialize the branch and update references once it exists.

Contribution model — prompts and issues over PRs. Continuing last week's thread, the group reaffirmed steering external contributions toward well-formed feature requests (prompts plus documentation) instead of raw pull requests. This keeps architectural control tight and avoids an unmaintained PR backlog.

SDK dependency minimization. The team committed to trimming the SDK's dependencies to simplify long-term maintenance and avoid cascading upgrade pain downstream.

Publishing / parallel beta releases. Shipping a beta alongside the stable line is still gated on publishing access. Cliff Hall will follow up with Den on the npm package controls, and the group wants automated beta publishing wired through changesets so pre-releases can go out without disturbing the stable channel.

Recruiting testers. Cliff Hall will post Discord requests for V2 Inspector testing and pull in internal teams for feedback; Konstantin will keep an eye on the channels through July for blocking issues.

Next Steps

• Cliff Hall: Initialize the servers-repo v2/main branch (copied from current main) and update branch references; contact Den about npm publishing controls to enable parallel beta releases; post Discord requests recruiting V2 Inspector testers and internal-team feedback.
• Bob Dickinson: Run the migration code mod against real code within days to identify missing exports or required hooks before the final release.
• Konstantin Konstantinov: Provide integration-test examples for the Inspector and monitor the channels through July for blocking issues.

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