SEP Guidelines changedcommunity/sep-guidelines
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 20 Oct 2026 20:07 UTC.
Upstream edited
Recorded here
Lines+8added
Lines−8removed
From line
71
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 71, old and new numbered
/
from line 71
7171
7272**Prior discussion is required.** SEP authors must discuss the idea with the relevant [working or interest group](/community/working-interest-groups) in [Discord](/community/communication#discord) before opening the SEP pull request, and the PR description must link to that discussion (a Discord thread, WG/IG meeting notes, or a GitHub Discussion). A SEP without a linked prior discussion is not accepted. If no relevant group exists, start a conversation in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) or the `#general` channel in [Discord](/community/communication#discord) instead. If there is enough interest, it may be worth [creating a new IG or WG](/community/working-interest-groups#creating-an-interest-group). The effort involved in finding sponsors and facilitators is a good signal of whether the idea has sufficient traction.
7373
74<Note>
75 To improve your chances of a SEP being accepted, check alignment with [Core
76 Maintainer](/community/governance#roles) priorities and [design
77 principles](/community/design-principles). Priorities are generally reflected
78 in the [project roadmap](/development/roadmap). Proposals outside current
79 priorities or that conflict with design principles are more likely to face
80 delays or additional friction in the review process.
81</Note>
74> [!NOTE]
75>
76> To improve your chances of a SEP being accepted, check alignment with [Core
77> Maintainer](/community/governance#roles) priorities and [design
78> principles](/community/design-principles). Priorities are generally reflected
79> in the [project roadmap](/development/roadmap). Proposals outside current
80> priorities or that conflict with design principles are more likely to face
81> delays or additional friction in the review process.
8282
83831. **Discuss with the relevant group**: Bring your idea to the matching [working or interest group](/community/working-interest-groups) and refine it there. Keep a link to the discussion (a Discord thread, meeting notes, or a GitHub Discussion) so you can include it in the PR description.
8484
No line in this hunk matches that.