Working and Interest Groups changedcommunity/working-interest-groups
Nearest release: v2.1.284, published 5 hours before 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 28 Sep 2026 22:47 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 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+5added
Lines−5removed
From line
81
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 81, old and new numbered
/
from line 81
8181
8282**Requirements for all Leads and Facilitators:**
8383
84* Hold at least Member status on the MCP Contributor Ladder — see [Governance](/community/governance) for role definitions
84* Hold at least Member status on the MCP Contributor Ladder — see [Governance](/community/governance.md) for role definitions
8585* Demonstrated sustained engagement with the group's scope area
8686* Ability to facilitate across organizational boundaries
8787* Commitment to running the group's operations
from line 102
102102
103103**WG Leads are additionally responsible for:**
104104
105* Drive proposals through the [SEP process](/community/sep-guidelines) to resolution
105* Drive proposals through the [SEP process](/community/sep-guidelines.md) to resolution
106106* Triage SEPs in the WG's scope area, including closing SEPs that do not fit the roadmap (with documented rationale; authors may appeal to Core Maintainers)
107107* Escalate blocked decisions to Core Maintainers with clear context
108108* Maintain the working group's roadmap
from line 226
226226**Working Group Formation:**
227227
228228* There must be a widely acknowledged concern requiring coordination
229* PR adding the WG charter as `docs/community/working-groups/<name>.mdx`, written from the [Group Charter Template](/community/charter-template) and including the corresponding navigation entry in `docs/docs.json`, gated by CODEOWNERS requiring approval from Core Maintainers
229* PR adding the WG charter as `docs/community/working-groups/<name>.mdx`, written from the [Group Charter Template](/community/charter-template.md) and including the corresponding navigation entry in `docs/docs.json`, gated by CODEOWNERS requiring approval from Core Maintainers
230230* Initial member list approved by WG Lead
231231
232232**Interest Group Formation:**
from line 252
252252
253253Every MCP Working Group and Interest Group must maintain a charter document that captures its specific mission, scope, leadership, membership, and operations. The governance rules above apply automatically and do not need to be repeated in the charter.
254254
255See the [Group Charter Template](/community/charter-template) for the required structure and a copyable template.
255See the [Group Charter Template](/community/charter-template.md) for the required structure and a copyable template.
256256
257257## FAQ
258258
from line 275
275275
276276### Do I need to be in a WG to submit a SEP?
277277
278No. Anyone can submit a SEP, and group membership is not required. The proposal must still be brought to the relevant group's Discord channel before the SEP pull request is opened, as described in the [SEP guidelines](/community/sep-guidelines#step-by-step-process). Beyond that requirement, closer WG collaboration can strengthen your proposal and help it find a sponsor.
278No. Anyone can submit a SEP, and group membership is not required. The proposal must still be brought to the relevant group's Discord channel before the SEP pull request is opened, as described in the [SEP guidelines](/community/sep-guidelines.md#step-by-step-process). Beyond that requirement, closer WG collaboration can strengthen your proposal and help it find a sponsor.
279279
280280### What if my IG discussion leads to a concrete solution?
281281
No line in this hunk matches that.