Skip to content

add: elicitation support #535

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
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

QuantGeekDev
Copy link
Contributor

@QuantGeekDev QuantGeekDev commented Jun 19, 2025

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

@QuantGeekDev QuantGeekDev changed the title Feature/elicitations Add Elicitation support Jun 19, 2025
@QuantGeekDev QuantGeekDev changed the title Add Elicitation support add: elicitation support Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant