Group Charter Template changedcommunity/charter-template
Nearest release: v2.1.321, published 5 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Nov 2026 13:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 9 Nov 2026 13:37 UTC.
Upstream edited
Recorded here
Lines+34added
Lines−69removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
## Submitting a charter ## Template ## Example Mission Statements
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Group Charter Template
22
3> Template for MCP Working Group and Interest Group charters.
3> The charter template for MCP working groups and interest groups, and how to submit a charter.
44
5Every MCP Working Group and Interest Group must maintain a charter document following this structure. Charters are stored at `docs/community/working-groups/<group-name>.mdx` or `docs/community/interest-groups/<group-name>.mdx` in the [modelcontextprotocol repository](https://github.com/modelcontextprotocol/modelcontextprotocol) and added to `docs/docs.json`.
5This page gives the charter template that every working group and interest group must follow and explains how to submit a charter. The template was adopted by [SEP-2149](https://modelcontextprotocol.io/seps/2149.md), a Specification Enhancement Proposal (SEP), and is changed, together with the rules in [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md), by a Process SEP. Each charter lives at `docs/community/working-groups/<name>.mdx` or `docs/community/interest-groups/<name>.mdx` in the [modelcontextprotocol repository](https://github.com/modelcontextprotocol/modelcontextprotocol), records only the group's mission, scope, leadership, membership and operations, and does not restate those rules, which apply to every group. Sections marked **(WG only)** are required for working groups and optional for interest groups. To start a group, see [Forming a group](https://modelcontextprotocol.io/community/working-interest-groups.md#forming-a-group).
66
7The charter captures information specific to your group. Governance rules — leadership requirements, decision-making process, meeting requirements, escalation paths — are defined in the [Working and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md) documentation and apply automatically. Do not repeat them here.
7## Submitting a charter
88
9Sections marked **(WG only)** are required for Working Groups and optional for Interest Groups.
9* The group must already be sponsored under [Forming a group](https://modelcontextprotocol.io/community/working-interest-groups.md#forming-a-group).
10* Copy the template below into the charter file and replace the placeholders. Delete the `{/* */}` guidance comments or leave them as written: HTML comments break the MDX build, and `npm run format` corrupts a `{/* */}` comment that spans lines.
11* Run `npm run prep`, then push.
12* Open a pull request that adds the charter file, a navigation entry under Working Groups or Interest Groups in `docs/docs.json`, and a line under [Current groups](https://modelcontextprotocol.io/community/working-interest-groups.md#current-groups).
13* A Core Maintainer will review the pull request, as outlined in the [Amending or retiring a group](https://modelcontextprotocol.io/community/working-interest-groups.md#amending-or-retiring-a-group) requirements.
14* Later changes follow [Amending or retiring a group](https://modelcontextprotocol.io/community/working-interest-groups.md#amending-or-retiring-a-group) and add a row to the charter's Changelog.
1015
1116> [!NOTE]
1217>
13> Copy the markdown below into `docs/community/working-groups/<group-name>.mdx` (or `interest-groups/` for an IG) and replace the placeholder text.
18> [Transports](https://modelcontextprotocol.io/community/working-groups/transports.md) and
19> [Security](https://modelcontextprotocol.io/community/interest-groups/security.md) are filled-in examples, for a
20> working group and an interest group respectively.
1421
15***
22## Template
1623
17```markdown theme={null}
24```mdx theme={null}
1825---
1926title: <Group Name> Charter
2027description: Charter for the MCP <Group Name> <Working Group | Interest Group>.
from line 29
2229
2330## Group Type
2431
25<!-- State whether this is a Working Group or an Interest Group. -->
32{/* Keep one, delete the other. */}
2633
2734**Working Group** | **Interest Group**
2835
2936## Mission Statement
3037
31<!--
32A 2-3 sentence summary of the group's purpose.
33- The problem space being addressed
34- Why cross-cutting collaboration is needed
35- For WGs: what concrete deliverables the group will produce
36- For IGs: what discussions and knowledge-sharing the group will facilitate
37-->
38{/* Two or three sentences: the problem space, why it needs collaboration across groups, and the deliverables the WG will produce or the discussions the IG will host. */}
39{/* Example opening: "The <Group Name> Working Group exists to <deliverable> so that <outcome>." */}
3840
3941## Scope
4042
4143### In Scope
4244
43<!--
44For WGs:
45- Specification Work: Specific spec sections or SEPs owned
46- Reference Implementations: SDK components or reference implementations
47- Cross-Cutting Concerns: Areas requiring coordination with other groups
48- Documentation: Documentation responsibilities
45{/* WG: Specification Work (spec sections or SEPs the group owns), Reference Implementations (SDK components or reference implementations), Cross-Cutting Concerns (areas needing coordination with other groups), and Documentation responsibilities. */}
46{/* IG: topic areas for discussion, and the kinds of output (problem statements, use cases, recommendations). */}
4947
50For IGs:
51- Topic areas for discussion
52- Types of output (problem statements, use cases, recommendations)
53-->
54
5548### Out of Scope
5649
57<!-- Explicit statements of what is NOT within the group's purview to prevent mission creep. -->
50{/* Explicit statements of what is not within the group's purview, to prevent mission creep. */}
5851
5952### Related Groups
6053
61<!-- List of other WGs or IGs with intersecting work and the nature of overlap. -->
54{/* Other WGs or IGs with intersecting work and the nature of the overlap. */}
6255
6356## Leadership
6457
65<!--
66Leadership requirements and responsibilities are defined in the governance rules.
67List current Leads (WG) or Facilitators (IG).
68-->
58{/* List current Leads (WG) or Facilitators (IG). Requirements and duties are defined at /community/working-interest-groups#leadership. */}
6959
7060| Role | Name | Organization | GitHub | Term |
7161| ---- | ---- | ------------ | ------ | ---- |
from line 63
7363
7464## Authority & Decision Rights (WG only)
7565
76<!--
77The decision-making process (lazy consensus → vote → escalation) is defined in
78the governance rules. This table documents which decisions this WG can make at
79which authority level.
66{/* The progression from lazy consensus to vote to escalation is defined at /community/working-interest-groups#making-decisions, not here. */}
67{/* The rows below record the level at which this WG takes each kind of decision. They are the usual allocation and are approved with the charter. A change to any row follows /community/working-interest-groups#amending-or-retiring-a-group and gets a Changelog row. */}
68{/* IGs do not make binding decisions and omit this section. */}
8069
81IGs do not make binding decisions and do not need this section.
82-->
83
8470| Decision Type | Authority Level |
8571| ----------------------------------- | ------------------------------------------------------ |
8672| Meeting logistics & scheduling | WG Leads (autonomous) |
from line 80
9480
9581## Membership
9682
97<!--
98List current group members and their participation levels, if any.
99Leave out if no members exist yet. Participation tiers and membership
100criteria are defined in the governance rules.
101-->
83{/* List current members and their participation level. Omit this section until the group has members. */}
84{/* Participation tiers and membership criteria are defined at /community/working-interest-groups#participation-levels. */}
10285
10386| Name | Organization | GitHub | Discord | Level |
10487| ---- | ------------ | ------ | ------- | ----- |
from line 89
10689
10790## Operations
10891
109<!--
110Document the group's current meeting approach. Meeting requirements (open,
111published 7 days ahead, agendas/notes to GitHub Discussions) and communication
112channels are defined in the governance rules.
113-->
92{/* List the group's regular meetings. Meeting and channel rules are defined at /community/working-interest-groups#meetings-and-channels. */}
93{/* External repositories, proposal documents or meeting notes may be listed below the table. */}
11494
11595| Meeting | Frequency | Duration | Purpose |
11696| --------------- | --------- | -------- | ------------------------------------- |
from line 99
11999
120100## Deliverables & Success Metrics (WG only)
121101
122<!--
123Track active work items with status and ownership.
124IGs may optionally list current discussion topics or planned outputs here.
125-->
102{/* IGs may list current discussion topics or planned outputs here instead. */}
126103
127104### Active Work Items
128105
129| Item | Status | Target Date | Champion |
130| ------------- | ------------------------- | ----------- | -------- |
131| SEP-XXX: Name | Draft / Review / Approved | | |
106| Item | Status | Target Date | Champion |
107| -------------- | ---------------------------- | ----------- | -------- |
108| SEP-XXXX: Name | draft / in-review / accepted | | |
132109
133110### Success Criteria
134111
135<!-- Measurable outcomes for WG success. -->
112{/* State measurable outcomes. */}
136113
137114## Changelog
138115
from line 117
140117| ---- | ------ |
141118| | |
142119```
143
144***
145
146## Example Mission Statements
147
148**Working Group:**
149
150> 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.
151
152**Interest Group:**
153
154> The Enterprise IG explores the challenges of deploying MCP in enterprise environments, gathering use cases and requirements to inform future specification work.
155120
No line in this hunk matches that.