SEP-2149: MCP Group Governance and Charter Template

---

​

Abstract

This SEP establishes governance rules and a standardized charter template for MCP’s two collaborative group types: Working Groups (WGs) and Interest Groups (IGs). Working Groups produce concrete deliverables — SEPs, implementations, and code. Interest Groups facilitate discussion and knowledge-sharing to identify problems and gather requirements. The governance rules define the requirements that all groups must follow, with lighter expectations for IGs where appropriate. The charter template defines the structure each group uses to document its specific mission, scope, leadership, and work. Together they address community feedback about unclear authority delegation and inconsistent processes across groups.

​

Motivation

Community interviews and feedback identified several challenges with the current group structure:

1. Unclear Authority: It’s not always clear what decisions a working group can make autonomously versus what requires Core Maintainer approval. This leads to hesitation and bottlenecks.
2. Inconsistent Decision-Making: Different groups operate with different norms. Decisions made in one meeting may be contradicted in another, with no clear process for resolution.
3. Participation Confusion: Community members are uncertain about who should participate in groups, what levels of involvement exist, and how to become more involved.
4. Scope Creep: Without explicit boundaries, groups may gradually expand into areas owned by other groups or outside their mandate.
5. Missing Escalation Paths: When groups get stuck, there’s no clear path to resolution, leading to prolonged disagreements or abandoned initiatives.
6. WG/IG Distinction: The difference between Working Groups and Interest Groups is not always clear to participants, leading to mismatched expectations about outputs and commitment.

A standardized charter template and shared governance rules address these issues by establishing consistent processes across all groups while requiring each group to explicitly define its specific scope and boundaries.

​

Specification

MCP maintains two types of collaborative groups:

• Working Groups (WGs) produce concrete deliverables — SEPs, reference implementations, and code. Active contribution is expected.
• Interest Groups (IGs) facilitate discussion and knowledge-sharing around a topic area. They produce problem statements, use cases, and recommendations. Active contribution is expected.

This specification has two parts:

1. Group Governance — rules that apply to all MCP groups (WGs and IGs), with differences noted where applicable
2. Charter Template — the structure each group fills in to define its specific mission, scope, and operations

---

​

Part 1: Group Governance

The following rules apply to all MCP Working Groups and Interest Groups. Individual charters cannot override these requirements. Where rules differ between WGs and IGs, this is noted explicitly.

​

1.1 Leadership

Each group has one or more Leads. Requirements for all Leads:

• Ability to facilitate across organizational boundaries
• Commitment to running the group’s operations

Additional requirements for WG Leads:

• Demonstrated sustained contribution to the WG’s scope area
• Commitment to 2-3 hours/week for WG activities
• Sponsored by at least two Core Maintainers or one Lead Core Maintainer

​

1.2 Leadership Responsibilities

All Leads are responsible for:

• Schedule and facilitate regular meetings
• Set agendas in collaboration with participants and publish them in advance
• Ensure meeting notes are published within 48 hours
• Maintain the group’s documentation
• Maintian a members list and respctive access list in https://github.com/modelcontextprotocol/access
• Proactively recruit and retain broad, representative membership across organizations and perspectives

WG Leads are additionally responsible for:

• Drive proposals through the SEP (Specification Enhancement Proposal) process to resolution
• Escalate blocked decisions to Core Maintainers with clear context
• Maintain the working group’s roadmap
• Solicit feedback from one or more Core Maintainers on the general direction of the group on a continuous basis
• Provide quarterly status updates to the Community and Core Maintainer Group

​

1.3 Participation Levels

All groups use the following participation tiers: Interest Groups primarily operate with Observers, Participants, and Facilitators. IGs may adopt the Member tier if their work warrants formal decision-making, but are not required to. Becoming a Member (WGs, and IGs that adopt the Member tier):

• Sustained participation over 3 months
• Meaningful contributions (code, spec text, reviews, or documentation)
• Nomination by existing Member or Lead
• No objections from Leads, Core Maintainers, or Lead Core Maintainers within 7 days

Member Responsibilities:

• Continue contributing in good faith
• Maintain name, organization, and Discord name in the respective group’s member list

Active vs. Emeritus: Members who do not participate for 3 consecutive months are moved to emeritus status and may return by demonstrating renewed participation.

​

1.4 Decision-Making Process

This section applies primarily to Working Groups, which make binding decisions (consensus on technical designs, spec changes, etc.). Interest Groups typically operate by rough consensus in discussions and do not make binding decisions — their output is recommendations, problem statements, and use cases. IGs that adopt the Member tier may use this process for internal decisions. WG Consensus is achieved through the following progression. Each step is attempted before moving to the next: Step 1: Lazy Consensus (default)

• Proposals announced with clear deadline (5 days minimum for minor items, 10 days for significant items)
• Silence is consent
• Any Member may block with documented objection
• Blocks must propose alternatives or clear criteria for resolution
• If no blocks are raised by the deadline, the proposal is accepted

Step 2: Formal Vote (when lazy consensus is blocked) A formal vote is triggered when:

• A Member blocks during the lazy consensus period
• A Lead or three or more Members request a formal vote

Voting rules:

• Quorum: 50% of active Members
• Passage: Simple majority for routine matters; 2/3 majority for scope changes
• Core Maintainer feedback is advisory unless explicitly stated as binding
• All votes documented with rationale

Step 3: Escalation (when voting does not resolve) If a vote fails to resolve the matter (no quorum, does not pass, or the result is contested), the Lead escalates to Core Maintainers following the escalation path defined below.

​

1.5 Escalation Path

For technical and design disagreements within a group’s scope, groups should resolve disagreements locally before involving Core Maintainers. For WGs, this means using the decision-making progression (lazy consensus → vote → escalation). For IGs, the Facilitator should attempt to find rough consensus before escalating. Some disagreements are not appropriate for group-level resolution and should be escalated directly to Core Maintainers:

• Scope disputes (whether a topic falls within the group’s charter)
• Authority disputes (whether the group has the right to decide a matter)
• Cross-group conflicts (disagreements spanning multiple WGs or IGs)
• Code of conduct or behavioral concerns
• Membership or participation disputes

When escalation is necessary:

1. Lead documents the decision, options considered, and points of disagreement
2. Lead presents the escalation to the Core Maintainer group with a clear ask
3. The Core Maintainer group designates a CM—who should not share organizational affiliation with the parties involved—to resolve the issue and report back to the group
4. The designated CM either: (a) provides binding guidance, (b) requests more information, or (c) recommends the full Core Maintainer group deliberate
5. Timeline: Escalations should receive initial response within 5 business days

​

1.6 Meeting & Communications Requirements

Leads determine meeting frequency, format, and duration based on the group’s current needs and lifecycle stage. There is no fixed cadence requirement — a WG near a specification release may meet weekly, while an IG in early exploration may meet monthly or work primarily asynchronously. Regardless of format or frequency, all group meetings must:

• Be open to all community participants (no closed or organization-internal meetings)
• Be published on meet.modelcontextprotocol.io at least 7 days in advance
• Have agendas published at least 24 hours in advance to a GitHub Discussion in the Meeting Notes category
• Have notes published within 48 hours to the same discussion

Leads should actively involve Members and Participants in operational duties such as preparing agendas, taking meeting notes, and facilitating discussions.

​

1.7 Communication Channels

All groups use the following channels: In addition to Discord, groups can establish a discussion category in the GitHub Discussions. Leads will be granted the appropriate roles to manage and moderate discussions.

​

1.8 Reporting

Working Groups provide quarterly updates (end of January, April, July, October) including:

• Progress against deliverables
• Blocked items and escalations
• Membership changes
• Upcoming priorities
• Resource needs

Interest Groups do not have formal reporting requirements but should keep their charter and member list current.

​

1.9 Lifecycle

Working Group Formation:

• There must be a cross-cutting concern requiring coordination
• PR for creation of WG into community/<name>/overview.mdx, gated by CODEOWNERS requiring approval by Maintainers
• PR for charter into community/<name>/charter.mdx, gated by CODEOWNERS requiring approval from Core Maintainers
• Initial member list approved by WG Lead

Interest Group Formation:

• Fill out the creation template in the #wg-ig-group-creation channel on Discord
• A community moderator reviews and calls for a vote in #community-moderators (72h period, majority approval)
• Once approved, the Facilitator(s) organize the IG and create a charter

Retirement:

• WGs: WG Lead or Core Maintainer proposes retirement with rationale; Core Maintainer or Lead Core Maintainer approval required. WGs are also retired when they have no active work for a sustained period or have completed all planned deliverables.
• IGs: Community moderators or Core/Lead Maintainers may retire an IG that is no longer active or needed.
• In both cases, documentation is archived and channels are marked inactive.

​

1.10 Charter Amendments

Changes to a group’s charter require:

• Proposal by Lead/Facilitator or Core Maintainer
• For WGs: Approval by Core Maintainers
• For IGs: Approval by community moderators

---

​

Part 2: Charter Template

Every MCP Working Group and Interest Group must maintain a charter document following this template structure. Charters are stored as MDX files in docs/community/ in the modelcontextprotocol repository and added to the docs.json file. The charter captures information specific to each group. Governance rules from Part 1 apply automatically and do not need to be repeated in the charter. Sections marked (WG only) are required for Working Groups but optional for Interest Groups.

​

1. Group Type

State whether this is a Working Group or an Interest Group.

​

2. Mission Statement

A 2-3 sentence summary of the group’s purpose, articulating:

• The problem space being addressed
• Why cross-cutting collaboration is needed
• For WGs: what concrete deliverables the group will produce
• For IGs: what discussions and knowledge-sharing the group will facilitate

WG Example: “The Transport Working Group exists to evolve MCP’s transport mechanisms to support diverse deployment scenarios—from local subprocess communication to horizontally-scaled cloud deployments—while maintaining protocol coherence and backward compatibility.” IG Example: “The Enterprise IG explores the challenges of deploying MCP in enterprise environments, gathering use cases and requirements to inform future specification work.”

​

3. Scope

In Scope: Enumerated responsibilities. For WGs, this includes:

• Specification Work: Specific spec sections or SEPs owned
• Reference Implementations: SDK components or reference implementations
• Cross-Cutting Concerns: Areas requiring coordination with other groups
• Documentation: Documentation responsibilities

For IGs, this includes:

• Topic areas for discussion
• Types of output (problem statements, use cases, recommendations)

Out of Scope: Explicit statements of what is NOT within the group’s purview to prevent mission creep. Related Groups: List of other WGs or IGs with intersecting work and nature of overlap.

​

4. Leadership

Leads/Facilitators table with:

• Role, Name, Organization, GitHub handle, Term

Leadership requirements and responsibilities are defined in the governance rules (Sections 1.1 and 1.2).

​

5. Authority & Decision Rights (WG only)

Each WG must explicitly define its decision authority. The decision-making process and escalation path are defined in the governance rules (Sections 1.4 and 1.5). This section documents which decisions the WG can make at which authority level. Example: IGs do not make binding decisions and do not need this section.

​

6. Membership

List current group members and their participation levels. Participation tiers and membership criteria are defined in the governance rules (Section 1.3).

​

7. Operations

Document the group’s current meeting approach. Meeting requirements and communication channels are defined in the governance rules (Sections 1.6 and 1.7). Example:

​

8. Deliverables & Success Metrics (WG only)

Active Work Items: Success Criteria: Measurable outcomes for WG success. Quarterly reporting requirements are defined in the governance rules (Section 1.8). IGs do not track formal deliverables but may list current discussion topics or planned outputs (problem statements, recommendations, etc.) in their charter.

​

9. Changelog

Track charter versions with date and changes.

​

Rationale

​

Why Separate Governance from Charter Template?

Separating fixed governance rules from the per-group charter template makes it clear what is consistent across all groups (decision-making, membership tiers, escalation) versus what each group defines for itself (scope, leadership roster, deliverables). This prevents groups from accidentally diverging on process while preserving flexibility where it matters.

​

Why Cover Both WGs and IGs?

Working Groups and Interest Groups serve different purposes but share common operational needs — leadership, meeting requirements, communication channels, and escalation paths. A unified governance framework ensures consistency while clearly articulating where IGs have lighter requirements (no formal decision authority, no deliverables tracking, no quarterly reporting).

​

Why a Standardized Template?

Standardization:

• Ensures all groups address critical governance questions
• Makes it easier for community members to understand any group’s operations
• Reduces overhead for forming new groups
• Creates accountability through explicit documentation

​

Why Explicit Authority Tables?

The authority table directly addresses the “unclear authority” feedback. By enumerating decision types and required approvals, WGs and community members know exactly what can be decided autonomously versus what needs escalation. IGs are exempt from this because they produce recommendations, not binding decisions.

​

Why Tiered Participation?

Different engagement levels serve different community needs:

• Observers can learn without commitment
• Participants can contribute without full Member responsibilities
• Members take on accountability and get decision rights (primarily WGs)
• Leads/Facilitators provide operational continuity

​

Why Lazy Consensus as Default?

Lazy consensus:

• Enables efficient decision-making for routine matters
• Reduces meeting burden
• Documents decisions through announcement/deadline structure
• Preserves blocking rights for substantive concerns

Voting is reserved for contested or high-impact decisions.

​

Model Inspiration

This template is adapted from Kubernetes governance structures and tailored for MCP’s specific needs identified through community interviews.

​

Backward Compatibility

​

Transition for Existing Groups

Working Groups and Interest Groups that exist at the time this SEP is accepted are grandfathered in — they are recognized as valid groups and do not need to re-apply through the formation process defined in Section 1.9. However, existing groups must create a charter conforming to the template in Part 2 within 8 weeks of this SEP’s acceptance. During this transition period:

• Existing groups continue to operate under their current processes
• Leads/Facilitators are responsible for drafting the charter
• Core Maintainers will review and approve WG charters; community moderators will review IG charters
• Groups that do not produce a charter within 8 weeks will be considered inactive and subject to retirement

​

Security Implications

No direct security implications. However, clear authority delegation and decision processes indirectly support security by ensuring decisions are made at appropriate levels with proper accountability.

​

Reference Implementation

Upon acceptance, this SEP will be implemented by:

1. Publishing the governance rules at docs/community/governance.mdx
2. Publishing the charter template at docs/community/charter-template.mdx
3. Adding governance and template guidance to the Working and Interest Groups section of modelcontextprotocol.io
4. Existing WGs and IGs updating their charters to conform within 8 weeks
5. Adding governance and charter documents to docs.json for website display