Skip to content

Conversation

@koic
Copy link
Member

@koic koic commented Nov 10, 2025

Motivation and Context

The MCP 2025-06-18 specification includes a feature called Elicitation:
https://modelcontextprotocol.io/specification/2025-06-18/client/elicitation

Like Log Level, an implementation is expected to be provided in the near future. This PR adds Elicitation as a skeleton implementation for now.

How Has This Been Tested?

The added test passes.

Breaking Changes

No breaking changes.

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

atesgoral
atesgoral previously approved these changes Nov 19, 2025
The MCP 2025-06-18 specification includes a feature called Elicitation:
https://modelcontextprotocol.io/specification/2025-06-18/client/elicitation

Like Log Level, an implementation is expected to be provided in the near future.
This PR adds Elicitation as a skeleton implementation for now.
@koic
Copy link
Member Author

koic commented Nov 24, 2025

@modelcontextprotocol/ruby-sdk The approval was dismissed when the conflict was resolved. Can you review it again when you have a moment?

@koic koic merged commit d31c3da into modelcontextprotocol:main Nov 24, 2025
5 checks passed
@koic koic deleted the add_elicitation_skeleton branch November 24, 2025 16:02
@koic
Copy link
Member Author

koic commented Nov 24, 2025

@atesgoral Thank you!

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.

2 participants