docs: remove extension approval mechanics

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8
This commit is contained in:
Sam Morrow 2026-08-12 09:22:46 +02:00
commit 99b6214b9d
No known key found for this signature in database

View file

@ -11,11 +11,9 @@ implementation; these priorities are intended to focus discussion and feedback.
Support maintainers and contributors in completing the Support maintainers and contributors in completing the
[planned transition of existing SEP proposals](./sep-disposition.md) into fully [planned transition of existing SEP proposals](./sep-disposition.md) into fully
fledged experimental extensions. The IG should gather use cases, coordinate fledged experimental extensions with SDK implementations. The IG should gather
review, and establish clear evidence that the community wants and will use each use cases, coordinate review, and establish clear evidence that the community
extension. Before an Extensions Track SEP is reviewed, wants and will use each extension.
[SEP-2133](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/2133-extensions.md)
requires at least one reference implementation in an official SDK.
## 2. Prepare Pre-flight Requests for Review ## 2. Prepare Pre-flight Requests for Review
@ -34,8 +32,7 @@ agents need.
[PR #7 proposes the `io.modelcontextprotocol/display-templates` experimental extension](https://github.com/modelcontextprotocol/experimental-ext-tool-annotations/pull/7) [PR #7 proposes the `io.modelcontextprotocol/display-templates` experimental extension](https://github.com/modelcontextprotocol/experimental-ext-tool-annotations/pull/7)
for this purpose, covering both call-side display templates and result-side for this purpose, covering both call-side display templates and result-side
rendered text. This belongs in the chartered discussion of tool-response rendered text. This belongs in the chartered discussion of tool-response
annotations and human-in-the-loop requirements, while any specification change annotations and human-in-the-loop requirements.
would still proceed through the SEP process.
## 4. Evaluate Annotation Proposals ## 4. Evaluate Annotation Proposals