Clarifications on mcp-server-card dynamic flag#2265
Closed
maiargu wants to merge 9 commits intomodelcontextprotocol:sep/mcp-server-cardsfrom
Closed
Clarifications on mcp-server-card dynamic flag#2265maiargu wants to merge 9 commits intomodelcontextprotocol:sep/mcp-server-cardsfrom
dynamic flag#2265maiargu wants to merge 9 commits intomodelcontextprotocol:sep/mcp-server-cardsfrom
Conversation
…l#1804) * Migrate final and closed SEPs to seps/ directory Migrate 10 SEPs with 'final' status or closed state to the new seps/ markdown format: - SEP-932: Model Context Protocol Governance - SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts - SEP-985: Align OAuth 2.0 Protected Resource Metadata with RFC 9728 - SEP-986: Specify Format for Tool Names - SEP-990: Enable enterprise IdP policy controls during MCP OAuth flows - SEP-994: Shared Communication Practices/Guidelines - SEP-1046: Support OAuth client credentials flow in authorization - SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance - SEP-1319: Decouple Request Payload from RPC Methods Definition - SEP-1330: Elicitation Enum Schema Improvements and Standards Compliance Also includes the migration script (migrate_seps.js) for future use. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Migrate final and closed SEPs to seps/ directory - Migrate 10 final/closed SEPs from GitHub issues to seps/ directory - Generate SEP documentation pages in docs/community/seps/ - Fix malformed Type fields in SEP-973, SEP-1319, SEP-1330 - Add complete content for SEP-1319 (was header-only) * Improve SEP sidebar: show titles and group by status - Add SEP titles to sidebar (truncated at 40 chars with ellipsis) - Group SEPs by status (Final, Accepted, Draft, etc.) in navigation - Makes sidebar more informative and less overwhelming --------- Co-authored-by: Claude <noreply@anthropic.com>
…1002 The SEP was previously just a placeholder. Added complete content based on the communication guidelines implementation in docs/community/communication.mdx.
…ontextprotocol#2136) Add 10 SEPs that were missed during the initial migration in PR modelcontextprotocol#1804: - SEP-991: OAuth Client ID Metadata Documents (Final) - SEP-1024: MCP Client Security Requirements (Final - PR modelcontextprotocol#1025 merged) - SEP-1034: Default values for elicitation schemas (Final) - SEP-1036: URL Mode Elicitation (Final) - SEP-1303: Input Validation Errors (Final) - SEP-1577: Sampling With Tools (Final) - SEP-1613: JSON Schema 2020-12 Default Dialect (Final) - SEP-1686: Tasks (Final) - SEP-1699: SSE Polling via server-side disconnect (Final) - SEP-1730: SDKs Tiering System (Final) Note: SEP-1309 (Specification Version Management) was NOT included as PR modelcontextprotocol#1404 implementing it is still open. Also fixes formatting issues in SEP metadata (Type, Author fields).
sdatapix
reviewed
Feb 17, 2026
| 5. **resources** (object, optional): Resource support | ||
| 1. **subscribe** (boolean, optional): Subscription support | ||
| 2. **listChanged** (boolean, optional): Change notification support | ||
| 2. **listChanged** (boolean, optional): Server runtime change notification support for the client when its resources list has changed |
There was a problem hiding this comment.
Thanks @maiargu Should this not be false when resources is not dynamic? That needs to be mentioned here as well.
Same comment applies to Tools change too.
Author
There was a problem hiding this comment.
Thanks @sdatapix , I added an additional statement to clearly mention this in the newly created 2269 PR, please further check there.
Author
|
Ups, my fork was not in sync. Closing in favour of #2269 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Clarifications on mcp-server-card
dynamicflagBuilds on #2127
The scope of this PR is strictly limited to provide clarifications for point
2.from @tadasant commentWhether to have dynamic as a value in tools/primitives?The answer to this question is probably
NO.A dynamic flag is not necessary to be introduced, if a MCP primitive is "dynamic" or not can be already expressed by using the
listChangedflag from the MCP protocol itself.This PR incorporates feedback from @Fannon comment
And solves concerns about "dynamic" raised by: