Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · mcp

Feature Lifecycle and Deprecation Policy changedcommunity/feature-lifecycle

Nearest release: v2.1.166, published 2 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 5 Jun 2026 16:12 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+10added
Lines−10removed
From line 16 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits3to this page, all time

The whole hunk

from line 16, old and new numbered
/
lines
from line 16
1616This policy governs **features** of the MCP core specification: protocol
1717messages, capabilities, transports, schema types, and normative behavioral
1818requirements. The revision lifecycle of the specification document itself
19(Draft, Current, Final) is defined in the [versioning guide](/docs/learn/versioning).
19(Draft, Current, Final) is defined in the [versioning guide](/docs/learn/versioning.md).
2020 
2121## Feature States
2222 
from line 52
5252* or any other reasons the Core Maintainers deem appropriate.
5353 
5454Deprecation is a specification change and therefore requires a SEP per the
55[SEP guidelines](/community/sep-guidelines). The deprecation SEP must:
55[SEP guidelines](/community/sep-guidelines.md). The deprecation SEP must:
5656 
57571. Identify the feature by name and link to its definition in `schema.ts`
5858 (where applicable) and the specification prose.
from line 85
8585 removal.
8686 
8787The feature becomes Deprecated when the revision carrying these changes is released
88and becomes the new Current revision (see [versioning guide](/docs/learn/versioning)).
88and becomes the new Current revision (see [versioning guide](/docs/learn/versioning.md)).
8989The minimum deprecation window is counted from that release.
9090 
9191## The Deprecated Registry
from line 112
112112 logger).
113113 
114114A Tier 1 SDK that consistently fails to surface a Deprecated feature is subject to the
115[Tier Relegation Process](/community/sdk-tiers#tier-relegation).
115[Tier Relegation Process](/community/sdk-tiers.md#tier-relegation).
116116 
117117## Removing a Feature
118118 
from line 132
132132security risk, meaning a vulnerability with a published security advisory or
133133documented in-the-wild exploitation for which no in-place mitigation exists.
134134Shortening the window requires Core Maintainer approval under the
135[governance decision process](/community/governance#decision-process), recorded
135[governance decision process](/community/governance.md#decision-process), recorded
136136in the deprecation SEP or, where the risk surfaces after that SEP is already
137137Final, in a short expedited-removal SEP that references it. The shortened
138138window must still provide at least ninety days between the feature becoming
from line 144
144144| - | - |
145145| Propose deprecation, extension, or restoration | Any contributor, per the SEP process |
146146| Sponsor | A Maintainer or Core Maintainer, per the SEP process |
147| Approve a deprecation SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
148| Decide a removal during release preparation | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
149| Approve an extension or restoration SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
150| Approve expedited removal | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
147| Approve a deprecation SEP | Core Maintainers, per the [governance decision process](/community/governance.md#decision-process) |
148| Decide a removal during release preparation | Core Maintainers, per the [governance decision process](/community/governance.md#decision-process) |
149| Approve an extension or restoration SEP | Core Maintainers, per the [governance decision process](/community/governance.md#decision-process) |
150| Approve expedited removal | Core Maintainers, per the [governance decision process](/community/governance.md#decision-process) |
151151 
152152Lead Maintainers retain veto authority over each of the approvals
153above, per the [governance roles](/community/governance#roles) definition.
153above, per the [governance roles](/community/governance.md#roles) definition.
154154 
Feedback