From 8809e9d4d89b00efcda5592ae3eb51bdbbf870fd Mon Sep 17 00:00:00 2001 From: olaservo Date: Mon, 4 Aug 2025 08:13:32 -0700 Subject: [PATCH 01/10] Add draft Inspector Roadmap --- roadmap.md | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 roadmap.md diff --git a/roadmap.md b/roadmap.md new file mode 100644 index 000000000..ded832cdc --- /dev/null +++ b/roadmap.md @@ -0,0 +1,39 @@ +# MCP Inspector Roadmap + +Timeline is TBD - this preliminary draft is to collect categories of improvements and discuss them with the maintainers group. + +Next steps after deciding on what is highest priority would be to set up a simple Project in the repo and reference the exact issues there. + +## CLI Mode + +We have a few PRs and issues open around these: + +- Add configuration parity with UI mode +- Add feature parity with UI mode + +We've also discussed separating this out into a dedicated repo, if that would help with maintainability. + +## UX Improvements (UI Mode) + +- Revisit UI design? +- Add ability to edit/add arbitrary headers +- TODO: Call out any other specific enhancements/bugs that we think are significant + +## Automation/General Process Improvements + +- Automatic dependency updates with Dependabot (SDK, etc.) +- Automation with Claude Code Github Action: + - Initial pass at PR review + - Initial pass at issue triage/labeling + - Opening PRs for simple bugs + - Needs references to MCP spec/docs and example tools for testing +- Revisit how we want to label issues and PRs +- Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing on-demand? + +## LLM Integration + +We previously decided not to include this, but people are finding it useful in alternative testing apps. Our previous concerns were around maintainability and whether this really belongs in Inspector. + +Examples: +- Chat functionality to test MCP features +- Real sampling with an LLM From 66176d7636d7d3bba5dc3e8fbda3f86d51b444da Mon Sep 17 00:00:00 2001 From: olaservo Date: Mon, 4 Aug 2025 08:23:21 -0700 Subject: [PATCH 02/10] Add note on voting on features --- roadmap.md | 1 + 1 file changed, 1 insertion(+) diff --git a/roadmap.md b/roadmap.md index ded832cdc..8873e537e 100644 --- a/roadmap.md +++ b/roadmap.md @@ -28,6 +28,7 @@ We've also discussed separating this out into a dedicated repo, if that would he - Opening PRs for simple bugs - Needs references to MCP spec/docs and example tools for testing - Revisit how we want to label issues and PRs +- Should we be actively taking thumbs up/voting into account for feature requests? - Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing on-demand? ## LLM Integration From 931ec7dac8b793dcad78e6212a197f51a04fde47 Mon Sep 17 00:00:00 2001 From: olaservo Date: Tue, 5 Aug 2025 05:05:24 -0700 Subject: [PATCH 03/10] Refine MCP Inspector Roadmap by clarifying sections and improving formatting --- roadmap.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/roadmap.md b/roadmap.md index 8873e537e..dab24f899 100644 --- a/roadmap.md +++ b/roadmap.md @@ -1,23 +1,22 @@ # MCP Inspector Roadmap -Timeline is TBD - this preliminary draft is to collect categories of improvements and discuss them with the maintainers group. +This preliminary draft is to collect categories of improvements and discuss them with the maintainers group. Next steps after deciding on what is highest priority would be to set up a simple Project in the repo and reference the exact issues there. ## CLI Mode -We have a few PRs and issues open around these: - -- Add configuration parity with UI mode -- Add feature parity with UI mode - -We've also discussed separating this out into a dedicated repo, if that would help with maintainability. +- Configuration parity with UI mode +- Feature parity with UI mode +- Would separating the CLI out into a dedicated repo help with maintainability? ## UX Improvements (UI Mode) -- Revisit UI design? -- Add ability to edit/add arbitrary headers -- TODO: Call out any other specific enhancements/bugs that we think are significant +- Not all configs are saved consistently +- Configs file support is inconsistent between modes +- Ability to edit/add arbitrary headers +- Editing long sets of args (or other long values) in the sidebar text boxes is annoying +- Revisit UI design ## Automation/General Process Improvements @@ -29,7 +28,8 @@ We've also discussed separating this out into a dedicated repo, if that would he - Needs references to MCP spec/docs and example tools for testing - Revisit how we want to label issues and PRs - Should we be actively taking thumbs up/voting into account for feature requests? -- Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing on-demand? +- Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand? + - And what can Claude be instructed to do with Playwright, etc? ## LLM Integration From 40db6a015511a04b226863f92eb5267d1908aef9 Mon Sep 17 00:00:00 2001 From: olaservo Date: Tue, 5 Aug 2025 05:06:23 -0700 Subject: [PATCH 04/10] Clarify testing references in automation section of MCP Inspector Roadmap --- roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roadmap.md b/roadmap.md index dab24f899..bb41181ab 100644 --- a/roadmap.md +++ b/roadmap.md @@ -25,7 +25,7 @@ Next steps after deciding on what is highest priority would be to set up a simpl - Initial pass at PR review - Initial pass at issue triage/labeling - Opening PRs for simple bugs - - Needs references to MCP spec/docs and example tools for testing + - Needs references to MCP spec/docs and example tools for testing (Ola has examples of this in personal repos to build on) - Revisit how we want to label issues and PRs - Should we be actively taking thumbs up/voting into account for feature requests? - Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand? From d06179dacb67e495367524567520d4cee2e392bc Mon Sep 17 00:00:00 2001 From: olaservo Date: Tue, 5 Aug 2025 05:08:18 -0700 Subject: [PATCH 05/10] Clarify testing references in automation section of MCP Inspector Roadmap --- roadmap.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/roadmap.md b/roadmap.md index bb41181ab..8db4ddc95 100644 --- a/roadmap.md +++ b/roadmap.md @@ -25,7 +25,9 @@ Next steps after deciding on what is highest priority would be to set up a simpl - Initial pass at PR review - Initial pass at issue triage/labeling - Opening PRs for simple bugs - - Needs references to MCP spec/docs and example tools for testing (Ola has examples of this in personal repos to build on) + - Needs references to MCP spec/docs and example tools for testing. Examples that could be incorporated into a 'Maintainer Toolkit MCP Server' or something similar: + - https://github.com/olaservo/mcp-advisor + - https://github.com/olaservo/mcp-misc/tree/main/example-tools - Revisit how we want to label issues and PRs - Should we be actively taking thumbs up/voting into account for feature requests? - Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand? From b283c9ae8d20080a37febd76c9135da6004a18b2 Mon Sep 17 00:00:00 2001 From: olaservo Date: Tue, 5 Aug 2025 19:39:29 -0700 Subject: [PATCH 06/10] Adding clarifications and improving the server management UI section --- roadmap.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/roadmap.md b/roadmap.md index 8db4ddc95..cd3a1658e 100644 --- a/roadmap.md +++ b/roadmap.md @@ -4,6 +4,8 @@ This preliminary draft is to collect categories of improvements and discuss them Next steps after deciding on what is highest priority would be to set up a simple Project in the repo and reference the exact issues there. +(Note that these aren't in any priority order yet, just collecting everything in one place.) + ## CLI Mode - Configuration parity with UI mode @@ -17,6 +19,7 @@ Next steps after deciding on what is highest priority would be to set up a simpl - Ability to edit/add arbitrary headers - Editing long sets of args (or other long values) in the sidebar text boxes is annoying - Revisit UI design +- Server selection and management UI - Surface config file in a chooser to allow closing one server and starting another from the UI ## Automation/General Process Improvements From 9684c2b9bd08edf3798a3414c2b2f4e1de43647d Mon Sep 17 00:00:00 2001 From: olaservo Date: Sun, 10 Aug 2025 16:06:56 -0700 Subject: [PATCH 07/10] Fix formatting --- roadmap.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/roadmap.md b/roadmap.md index cd3a1658e..05a0d0223 100644 --- a/roadmap.md +++ b/roadmap.md @@ -25,21 +25,22 @@ Next steps after deciding on what is highest priority would be to set up a simpl - Automatic dependency updates with Dependabot (SDK, etc.) - Automation with Claude Code Github Action: - - Initial pass at PR review - - Initial pass at issue triage/labeling - - Opening PRs for simple bugs - - Needs references to MCP spec/docs and example tools for testing. Examples that could be incorporated into a 'Maintainer Toolkit MCP Server' or something similar: - - https://github.com/olaservo/mcp-advisor - - https://github.com/olaservo/mcp-misc/tree/main/example-tools + - Initial pass at PR review + - Initial pass at issue triage/labeling + - Opening PRs for simple bugs + - Needs references to MCP spec/docs and example tools for testing. Examples that could be incorporated into a 'Maintainer Toolkit MCP Server' or something similar: + - https://github.com/olaservo/mcp-advisor + - https://github.com/olaservo/mcp-misc/tree/main/example-tools - Revisit how we want to label issues and PRs - Should we be actively taking thumbs up/voting into account for feature requests? - Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand? - - And what can Claude be instructed to do with Playwright, etc? + - And what can Claude be instructed to do with Playwright, etc? ## LLM Integration We previously decided not to include this, but people are finding it useful in alternative testing apps. Our previous concerns were around maintainability and whether this really belongs in Inspector. Examples: + - Chat functionality to test MCP features - Real sampling with an LLM From 32f4dc02a849be40d0407596c12ecc410948fc0f Mon Sep 17 00:00:00 2001 From: Ola Hungerford Date: Mon, 11 Aug 2025 07:43:49 -0700 Subject: [PATCH 08/10] Update roadmap.md --- roadmap.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/roadmap.md b/roadmap.md index 05a0d0223..207a8ac93 100644 --- a/roadmap.md +++ b/roadmap.md @@ -21,6 +21,11 @@ Next steps after deciding on what is highest priority would be to set up a simpl - Revisit UI design - Server selection and management UI - Surface config file in a chooser to allow closing one server and starting another from the UI +## OAuth Debugging and Compatibility Checking + +- Outh testing and debugging hiccups: see issues labeled `auth` for examples +- Client auth compatibility checker (See: https://github.com/modelcontextprotocol/inspector/pull/694/files) + ## Automation/General Process Improvements - Automatic dependency updates with Dependabot (SDK, etc.) From fc19a80d11515e879a8f96dd11ae11e10c7b4051 Mon Sep 17 00:00:00 2001 From: olaservo Date: Thu, 18 Sep 2025 07:10:01 -0700 Subject: [PATCH 09/10] Update WIP roadmap for 1.0 must haves --- roadmap.md | 57 +++++++++++++++++++----------------------------------- 1 file changed, 20 insertions(+), 37 deletions(-) diff --git a/roadmap.md b/roadmap.md index 207a8ac93..0135e96a3 100644 --- a/roadmap.md +++ b/roadmap.md @@ -1,51 +1,34 @@ -# MCP Inspector Roadmap +# MCP Inspector Roadmap for 1.0 -This preliminary draft is to collect categories of improvements and discuss them with the maintainers group. +This document outlines which features and bugs we plan to include for a 1.0 release. -Next steps after deciding on what is highest priority would be to set up a simple Project in the repo and reference the exact issues there. +(Note that these aren't all in priority order.) -(Note that these aren't in any priority order yet, just collecting everything in one place.) +## Auth Developer Experience -## CLI Mode +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. -- Configuration parity with UI mode -- Feature parity with UI mode -- Would separating the CLI out into a dedicated repo help with maintainability? +- 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) -- Not all configs are saved consistently -- Configs file support is inconsistent between modes -- Ability to edit/add arbitrary headers -- Editing long sets of args (or other long values) in the sidebar text boxes is annoying -- Revisit UI design -- Server selection and management UI - Surface config file in a chooser to allow closing one server and starting another from the UI +- Resolve any critical tool testing issues (revisit and resolve open PRs for handling defaults, nulls, nested values). +- TODO: Are there any other essential UX improvements we want to prioritize here? -## OAuth Debugging and Compatibility Checking +## CLI Mode Parity -- Outh testing and debugging hiccups: see issues labeled `auth` for examples -- Client auth compatibility checker (See: https://github.com/modelcontextprotocol/inspector/pull/694/files) +- Configuration parity with UI mode +- Feature parity with UI mode (excluding sampling and elicitation) ## Automation/General Process Improvements -- Automatic dependency updates with Dependabot (SDK, etc.) -- Automation with Claude Code Github Action: - - Initial pass at PR review - - Initial pass at issue triage/labeling - - Opening PRs for simple bugs - - Needs references to MCP spec/docs and example tools for testing. Examples that could be incorporated into a 'Maintainer Toolkit MCP Server' or something similar: - - https://github.com/olaservo/mcp-advisor - - https://github.com/olaservo/mcp-misc/tree/main/example-tools -- Revisit how we want to label issues and PRs -- Should we be actively taking thumbs up/voting into account for feature requests? -- Playwright tests vs ad-hoc testing - what makes sense to expand here as part of CI vs doing testing on-demand? - - And what can Claude be instructed to do with Playwright, etc? - -## LLM Integration - -We previously decided not to include this, but people are finding it useful in alternative testing apps. Our previous concerns were around maintainability and whether this really belongs in Inspector. - -Examples: +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. -- Chat functionality to test MCP features -- Real sampling with an LLM +- 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? From ffb0eefe100a15200a5ff2a93213b38223544069 Mon Sep 17 00:00:00 2001 From: olaservo Date: Thu, 18 Sep 2025 07:27:14 -0700 Subject: [PATCH 10/10] Add note to resolve critical issues with saving and editing server configs in UX Improvements --- roadmap.md | 1 + 1 file changed, 1 insertion(+) diff --git a/roadmap.md b/roadmap.md index 0135e96a3..5634ef231 100644 --- a/roadmap.md +++ b/roadmap.md @@ -14,6 +14,7 @@ OAuth and other auth-related debugging is especially valuable for MCP server dev ## 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