SEP-932: Model Context Protocol Governance - Model Context Protocol Documentation Index Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. Skip to main content Model Context Protocol home page Search... ⌘ K Ask Assistant ⌘ I * Blog * GitHub Search... Navigation Final SEP-932: Model Context Protocol Governance Documentation Specification Extensions Registry SEPs Community * SEP Index Final * SEP-414: Document OpenTelemetry Trace Context Pr… * SEP-932: Model Context Protocol Governance * SEP-973: Expose additional metadata for Implemen… * SEP-985: Align OAuth 2.0 Protected Resource Meta… * SEP-986: Specify Format for Tool Names * SEP-990: Enable enterprise IdP policy controls d… * SEP-991: Enable URL-based Client Registration us… * SEP-994: Shared Communication Practices/Guidelin… * SEP-1024: MCP Client Security Requirements for Lo… * SEP-1034: Support default values for all primitiv… * SEP-1036: URL Mode Elicitation for secure out-of-… * SEP-1046: Support OAuth client credentials flow i… * SEP-1302: Formalize Working Groups and Interest G… * SEP-1303: Input Validation Errors as Tool Executi… * SEP-1319: Decouple Request Payload from RPC Metho… * SEP-1330: Elicitation Enum Schema Improvements an… * SEP-1577: Sampling With Tools * SEP-1613: Establish JSON Schema 2020-12 as Defaul… * SEP-1686: Tasks * SEP-1699: Support SSE polling via server-side dis… * SEP-1730: SDKs Tiering System * SEP-1850: PR-Based SEP Workflow * SEP-1865: MCP Apps - Interactive User Interfaces… * SEP-2085: Governance Succession and Amendment Pro… * SEP-2106: Tools `inputSchema` & `outputSchema` Co… * SEP-2133: Extensions * SEP-2148: MCP Contributor Ladder * SEP-2149: MCP Group Governance and Charter Templa… * SEP-2164: Standardize Resource Not Found Error Co… * SEP-2207: OIDC-Flavored Refresh Token Guidance * SEP-2243: HTTP Header Standardization for Streama… * SEP-2260: Require Server requests to be associate… * SEP-2322: Multi Round-Trip Requests * SEP-2468: Recommend Issuer (iss) Parameter in MCP… * SEP-2484: Require Conformance Tests for Standards… * SEP-2549: TTL for List Results * SEP-2567: Sessionless MCP via Explicit State Hand… * SEP-2575: Make MCP Stateless * SEP-2577: Deprecate Roots, Sampling, and Logging * SEP-2596: Specification Feature Lifecycle and Dep… * SEP-2663: Tasks Extension On this page * Abstract * Motivation * Rationale * Hierarchical Structure * Individual vs Corporate Membership * SEP Process * Specification * Governance Structure * Contributors * Maintainers * Core Maintainers * Lead Maintainers * Backwards Compatibility * Reference Implementation * Security Implications Final SEP-932: Model Context Protocol Governance Copy page Copy page Model Context Protocol Governance Copy page Copy page Final Process This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to the current specification and its changelog for authoritative requirements. Field Value SEP 932 Title Model Context Protocol Governance Status Final Type Process Created 2025-07-08 Author(s) David Soria Parra Sponsor None PR #931 ​ Abstract This SEP establishes the formal governance model for the Model Context Protocol (MCP) project. It defines the organizational structure, decision-making processes, and contribution guidelines necessary for transparent and effective project stewardship. The proposal introduces a hierarchical governance structure with clear roles and responsibilities, along with the Specification Enhancement Proposal (SEP) process for managing protocol changes. ​ Motivation As the Model Context Protocol grows in adoption and complexity, the need for formal governance becomes critical. The current informal decision-making process lacks: * Transparency : Community members have no clear visibility into how decisions are made * Participation Pathways : Contributors lack defined ways to influence project direction * Accountability : No formal structure exists for resolving disputes or contentious issues * Scalability : Ad-hoc processes cannot scale with growing community and technical complexity Without formal governance, the project risks: * Fragmentation of the ecosystem * Unclear or inconsistent technical decisions * Reduced community trust and participation * Inability to effectively manage contributions at scale ​ Rationale The proposed governance model draws inspiration from successful open source projects like Python, PyTorch, and Rust. Key design decisions include: ​ Hierarchical Structure We chose a hierarchical model (Contributors → Maintainers → Core Maintainers → Lead Maintainers) that is effectively how the project decisions are made today. From there we will continue to evolve governance in the best interest of the project. ​ Individual vs Corporate Membership Membership is explicitly tied to individuals rather than companies to: * Ensure decisions prioritize protocol integrity over corporate interests * Prevent capture by any single organization * Maintain continuity when individuals change employers ​ SEP Process The Specification Enhancement Proposal process ensures: * All protocol changes undergo thorough review * Community input is systematically collected * Design decisions are documented for posterity * Implementation precedes finalization ​ Specification ​ Governance Structure ​ Contributors * Any individual who files issues, submits pull requests, or participates in discussions * No formal membership or approval required ​ Maintainers * Responsible for specific components (SDKs, documentation, etc.) * Appointed by Core Maintainers * Have write/admin access to their repositories * May establish component-specific processes ​ Core Maintainers * Deep understanding of MCP specification required * Responsible for protocol evolution and project direction * Meet bi-weekly for decisions * Can veto maintainer decisions by majority vote * Current members listed in governance documentation ​ Lead Maintainers * Justin Spahr-Summers and David Soria Parra * Can veto any decision * Appoint/remove Core Maintainers * Admin access to all infrastructure ​ Backwards Compatibility N/A ​ Reference Implementation See #931 * Documentation Files : * /docs/community/governance.mdx - Full governance documentation * /docs/community/sep-guidelines.mdx - SEP process guidelines ​ Security Implications N/A Was this page helpful? Yes No SEP-414: Document OpenTelemetry Trace Context Pr… SEP-973: Expose additional metadata for Implemen… github Assistant Responses are generated using AI and may contain mistakes.