Skip to main content
Specification Enhancement Proposals (SEPs) are the primary mechanism for proposing major changes to the Model Context Protocol. Each SEP provides a concise technical specification and rationale for proposed features.

Submit a SEP

Learn how to submit your own Specification Enhancement Proposal

Summary

  • Final: 11

All SEPs

SEPTitleStatusTypeCreated
SEP-1850PR-Based SEP WorkflowFinalProcess2025-11-20
SEP-1330Elicitation Enum Schema Improvements and Standards ComplianceFinalStandards Track2025-08-11
SEP-1319Decouple Request Payload from RPC Methods DefinitionFinalStandards Track2025-08-08
SEP-1302Formalize Working Groups and Interest Groups in MCP GovernanceFinalStandards Track2025-08-05
SEP-1046Support OAuth client credentials flow in authorizationFinalStandards Track2025-07-23
SEP-994Shared Communication Practices/GuidelinesFinalProcess2025-07-17
SEP-990Enable enterprise IdP policy controls during MCP OAuth flowsFinalStandards Track2025-06-04
SEP-986Specify Format for Tool NamesFinalStandards Track2025-07-16
SEP-985Align OAuth 2.0 Protected Resource Metadata with RFC 9728FinalStandards Track2025-07-16
SEP-973Expose additional metadata for Implementations, Resources, Tools and PromptsFinalStandards Track2025-07-15
SEP-932Model Context Protocol GovernanceFinalProcess2025-07-08

SEP Status Definitions

  • Draft - SEP proposal with a sponsor, undergoing informal review
  • In-Review - SEP proposal ready for formal review by Core Maintainers
  • Accepted - SEP accepted, awaiting reference implementation
  • Final - SEP finalized with reference implementation complete
  • Rejected - SEP rejected by Core Maintainers
  • Withdrawn - SEP withdrawn by the author
  • Superseded - SEP replaced by a newer SEP
  • Dormant - SEP without a sponsor, closed after 6 months