Inspector V2 Working Group Meeting - April 8, 2026 #2534
cliffhall
started this conversation in
Meeting Notes - Inspector V2 WG
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Inspector V2 Working Group Meeting - April 8, 2026
Agenda
@cliffhall to report on the state of the Storybook UI PR and next steps
@BobDickinson to discuss an MCP over CLI tool that he saw at the Dev Summit and whether its use cases should fall under our purview.
Attendees
Discussion
@cliffhall shared an update about the progress of the storybook components and the state of the UI. In addition to moving the components to a closer-to-usable state, he has created a document in the outstanding PR that describes a plan for refactoring the currently ad-hoc interfaces for the components to using real types from the MCP schema and the Inspector core (on v1.5 branch). This will prepare the UI for connecting to the actual data the InspectorClient will provide. He said the components are most of the way there, with only a few potential gaps in usage (sampling and elicitations happen one at a time in modals, but there are components for handling a pending list of either/both inline in the tool page).
@BobDickinson and @olaservo agreed the plan seemed like a sound next step and to review / approve the PR for merge so we can move on to the refactoring step. Bob mentioned the appearance of weasel words like "likely" appearing in the plan where it referenced types or their locations in the MCP schema or inspector core. This typically because the model didn't actually check the source of truth there and made something up.
@bob reported about an MCP over CLI tool that he saw at the Dev Summit which seemed interesting. It's a CLI for MCP, rather than a CLI version of the inspector, which is slightly different take. It lets you start many servers and manage them, sending CLI commands rather than making MCP calls. So clients that don't support resources or tasks, say, could actually use them via this CLI. Further discussion and demos to come in future meetings.
Next Steps
Operational Details
v2/mainbranch of the Inspector repov1.5/mainbranch of the Inspector repoBeta Was this translation helpful? Give feedback.
All reactions