Conversation
9 tasks
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
pwwpche
reviewed
Jan 23, 2026
dsp-ant
reviewed
Jan 23, 2026
kurtisvg
reviewed
Jan 23, 2026
pcarleton
reviewed
Jan 23, 2026
dsp-ant
reviewed
Jan 26, 2026
Member
dsp-ant
left a comment
There was a problem hiding this comment.
We should add the extension page outline to this PR.
48435c1 to
a6432a6
Compare
80b489c to
84bdbfd
Compare
CaitieM20
previously approved these changes
Jan 26, 2026
02e50c7 to
1a747b2
Compare
bhosmer-ant
previously approved these changes
Jan 26, 2026
Member
|
This was accepted by @modelcontextprotocol/core-maintainers unanimously: Voting results:
Once comments are addressed, this can be merged and status changed to final. @pja-ant please ensure that SDK's are implementing the necessary changes. |
Co-authored-by: Che Liu <cheliu@google.com>
Co-authored-by: Che Liu <cheliu@google.com>
- Update definition to be more flexible (modular, specialized, experimental) - Add collision prevention guidance for extension identifiers - Define what constitutes a breaking change - Add example links to MAINTAINERS.md files - Add SHOULD for working/interest groups - Add hyperlink to SEP guidelines - Require reference implementation before acceptance - Clarify minor updates don't need SEP review - Update graceful degradation to allow rejecting requests - Clarify backwards compatibility concerns for extensions - Update to RFC 2119 language throughout
- Add 'extensions' field to ClientCapabilities and ServerCapabilities in draft schema - Create extensions.mdx documentation page listing ext-auth and ext-apps - Add extensions navigation to docs.json under Community tab - Add Extension Negotiation section to lifecycle specification - Add example JSON files for extension capabilities - Regenerate schema.json and schema.mdx
The merge-base changed after approval.
1a747b2 to
f193987
Compare
localden
approved these changes
Jan 26, 2026
9 tasks
This was referenced Feb 4, 2026
7 tasks
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
9 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.
This SEP ports the Extensions proposal from issue #1724 to the new PR-based SEP format (per SEP-1850).
Summary
Establishes a framework for extending the Model Context Protocol while maintaining interoperability, clear governance, and appropriate legal structure.
Key Points
io.modelcontextprotocol/oauth-client-credentials)github.com/modelcontextprotocol/ext-*repositoriesextensionsfield in ClientCapabilities/ServerCapabilitiesDesign Consistency
The patterns described are consistent with existing official extensions (ext-apps and ext-auth).
References