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.
Added support for elicitation introduced in the 2025-06-18 specification update. Works across Tools, Resources and Prompts.
This PR depends on #532 for using elicitation from the sdk
Motivation and Context
Adds the ability for users to debug and test the new elicitation feature
How Has This Been Tested?
Here is a video showcasing the functionality and testing
Tested against a demo server I built to test elicitations mcp-elicitations server that implements elicitation in tools, prompts, and resources with the @modelcontextprotocol/[email protected]
The server is also accessible via this url
https://weekly-mink.mcpstudio.io/mcp
You can replicate results by checking out this branch, and connecting the inspector to the hosted server url via streamable-http. Then try to use any of the prompts, tools, or resources. I recommend increasing the request timeout in the inspector configuration
I would appreciate feedback on this - are modals a good way to represent elicitation in the inspector?
Breaking Changes
No, this is a new feature of the protocol that has to be specifically invoked in server code
Types of changes
Checklist