modelcontextprotocol/experimental-ext-tool-annotations
Watch
1
0
Fork
You've already forked experimental-ext-tool-annotations
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: remove extension approval mechanics

Browse source 
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
1 changed files with 4 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/next-spec-iteration-priorities.md
View file

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