Skip to content

Conversation

@findleyr
Copy link
Contributor

@findleyr findleyr commented Dec 9, 2025

To address #607, add ClientCapabilities.RootsV2, and populate it when constructing sending and receiving InitializeParams.

Fixes #607

@findleyr findleyr force-pushed the capabilities branch 2 times, most recently from 48e9682 to 332eb84 Compare December 9, 2025 00:58
To address modelcontextprotocol#607, add ClientCapabilities.RootsV2, and populate it when
constructing sending and receiving InitializeParams.

Also generally improve documentation for protocol types related to
capabilities.

Fixes modelcontextprotocol#607
markus-kusano
markus-kusano previously approved these changes Dec 9, 2025
jba
jba previously approved these changes Dec 9, 2025
Copy link
Contributor

@jba jba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After addressing Markus's comments.

@findleyr findleyr dismissed stale reviews from jba and markus-kusano via 23b1b68 December 10, 2025 19:03
@findleyr
Copy link
Contributor Author

PTAL: I renamed RootsCapabilities to RootCapabilities, to be consistent with ToolCapabilities, PromptCapabilities, etc.

(Almost another mistake!)

@findleyr
Copy link
Contributor Author

Gentle nudge: this needs reapproval as I address comments and made the nontrivial change to rename to RootCapabilities.

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.

How to check client capabilities and handle unsupported capability errors?

3 participants