Skip to content

Add Inspector Roadmap for v1.0 #676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
+35 −0
Open

Add Inspector Roadmap for v1.0 #676

Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
8809e9d
Add draft Inspector Roadmap
olaservo Aug 4, 2025
66176d7
Add note on voting on features
olaservo Aug 4, 2025
931ec7d
Refine MCP Inspector Roadmap by clarifying sections and improving for…
olaservo Aug 5, 2025
40db6a0
Clarify testing references in automation section of MCP Inspector Roa…
olaservo Aug 5, 2025
d06179d
Clarify testing references in automation section of MCP Inspector Roa…
olaservo Aug 5, 2025
8213db5
Merge branch 'main' into roadmap
olaservo Aug 6, 2025
b283c9a
Adding clarifications and improving the server management UI section
olaservo Aug 6, 2025
9684c2b
Fix formatting
olaservo Aug 10, 2025
32f4dc0
Update roadmap.md
olaservo Aug 11, 2025
41a1d6f
Merge remote-tracking branch 'upstream/main' into roadmap
olaservo Sep 18, 2025
fc19a80
Update WIP roadmap for 1.0 must haves
olaservo Sep 18, 2025
ffb0eef
Add note to resolve critical issues with saving and editing server co…
olaservo Sep 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# MCP Inspector Roadmap for 1.0

This document outlines which features and bugs we plan to include for a 1.0 release.

(Note that these aren't all in priority order.)

## Auth Developer Experience

OAuth and other auth-related debugging is especially valuable for MCP server developers. As the official debugging tool for MCP, Inspector can take advantage of working group expertise and oversight to support a robust and reliable auth debugging experience.

- TODO: see issues labeled `auth` and label any critical outstanding feature requests or open issues.
- Establish a simple process for Auth DX Working Group to help in reviewing and addressing auth-related issues and PRs going forward.

## UX Improvements (UI Mode)

- Resolve any critical tool testing issues (revisit and resolve open PRs for handling defaults, nulls, nested values).
- Resolve any critical issues with saving and/or editing server configs.
- TODO: Are there any other essential UX improvements we want to prioritize here?
Copy link
Member

@cliffhall cliffhall Sep 18, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I want the bottom drawer with notifications to be handled better. I hate having to drag it up/down because the affordance is so small. Click to open/minimize would be nice. Also when it is dragged up, it should be able to fill the screen. Right now it goes to a position that leaves an unusable part of the upper pane visible for no good reason.
  • Move ping to a button on the side panel, it doesn't need a whole pane.
  • Arrange the items in the auth debugger better, so that the continue button for guided flow isn't below the bottom pane's default position, forcing you to drag the pane down to see it.
  • Make tools be the default pane, not resources
  • Space the buttons at the top a bit more so that when a red notification counter appears on, say elicitations, it isn't clipped by the next button over


## CLI Mode Parity

- Configuration parity with UI mode
- Feature parity with UI mode (excluding sampling and elicitation)

## Automation/General Process Improvements

This includes everything that isn't already mentioned in "Auth Developer Experience" above. These aren't really tied to a release version but we should still plan to review and address them in that timeframe.

- TODO: Automation with Claude Code Github Action:
- Should we use Claude for an initial pass at issue triage/labeling?
- Any other low hanging fruit for automation?
- TODO: Revisit how we want to label issues and PRs
- TODO: Should we be actively taking thumbs up/voting into account for feature requests?
- TODO: Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand?
- Can Claude be instructed to handle additional regression testing with Playwright, etc?
Loading