SEP Guidelines changedcommunity/sep-guidelines
Nearest release: v2.1.314, published 12 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 29 Oct 2026 11:37 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 29 Oct 2026 12:07 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line
39
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
The whole hunk
from line 39, old and new numbered
/
from line 39
39391. **Standards Track** - Describes a new feature or implementation for the Model Context Protocol, or an interoperability standard supported outside the core specification.
40402. **Informational** - Describes a design issue or provides guidelines/information to the community without proposing a new feature.
41413. **Process** - Describes a process surrounding MCP or proposes a change to a process (like this document).
424. **Extensions Track** - Describes a protocol extension. Follows the same review and acceptance process as Standards Track SEPs, but indicates that the proposal is for an extension rather than a protocol addition. See [Creating Extensions](https://modelcontextprotocol.io/extensions/overview.md#creating-extensions) for the extension lifecycle.
424. **Extensions Track** - Describes a protocol extension. Follows the same review and acceptance process as Standards Track SEPs, but indicates that the proposal is for an extension rather than a protocol addition. An accepted Extensions Track SEP moves an extension to Beta, and a second one moves it to Stable. See [Extension Lifecycle](https://modelcontextprotocol.io/extensions/overview.md#extension-lifecycle) for the stages.
4343
4444## SEP Workflow
4545
No line in this hunk matches that.