-
Notifications
You must be signed in to change notification settings - Fork 885
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.
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
olaservo
wants to merge
12
commits into
modelcontextprotocol:main
Choose a base branch
from
olaservo:roadmap
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+35
−0
Open
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 66176d7
Add note on voting on features
olaservo 931ec7d
Refine MCP Inspector Roadmap by clarifying sections and improving for…
olaservo 40db6a0
Clarify testing references in automation section of MCP Inspector Roa…
olaservo d06179d
Clarify testing references in automation section of MCP Inspector Roa…
olaservo 8213db5
Merge branch 'main' into roadmap
olaservo b283c9a
Adding clarifications and improving the server management UI section
olaservo 9684c2b
Fix formatting
olaservo 32f4dc0
Update roadmap.md
olaservo 41a1d6f
Merge remote-tracking branch 'upstream/main' into roadmap
olaservo fc19a80
Update WIP roadmap for 1.0 must haves
olaservo ffb0eef
Add note to resolve critical issues with saving and editing server co…
olaservo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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? | ||
|
||
## 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? |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.