You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WG: review agents-wg PR 22 (agent discovery SEP) with experimental/ext/agents as a second implementation #1238
Carried out of #1142. The implementation shipped in August. The outreach it gated has partly happened, and the target has moved.
What changed since this was filed
The research PR (agents-wg PR 20) became a draft Extensions Track SEP, agents-wg PR 22 "MCP Agent Discovery Extension" (madhaviai, sponsored by LucaButBoring, opened 2026-08-20). Review happens there.
The SEP answered the envelope question. It advertises under capabilities.extensions, as mcpkit does.
mcpkit moved its extension ID to io.mcpkit/agents (7d66469f) until the shape is ratified.
2026-09-17: first comment posted. Review comment 4032278568 asked who enforces the "agents/get tools also appear in tools/list" rule. Head bfc43abb answered it the same day (servers SHOULD validate at configuration time, per-request responses MUST reflect the caller's authorization) and also listed "agent exposed as a single tool" as a rejected alternative.
2026-09-18: no runnable agents example remains in mcpkit.f24f478d removed examples/agents/deep-agent-supervisor. examples/agents/kitchen-sink does not register agents.
What's still owed
Review feedback on agents-wg PR 22, revised against bfc43abb and surfaced here for approval before posting (draft in mcpcontrib proposals/agents-wg/pr22-comments-draft.md):
Pre-merge identifier (draft A.1). Ask what identifier implementations should use for cross-implementation testing before the SEP merges, given mcpkit ships io.mcpkit/agents to avoid squatting the final name.
Stateless datapoint (draft A.3). SEP-2575 parity came for free because only discovery is new wire surface (TestStatelessWireParity).
Step-up questions (draft C, trimmed).bfc43abb adds a MAY for step-up on known-but-unauthorized agents. Two questions remain open: how agent-level gating relates to per-tool authorization, and whether the roster itself should hide agents the caller cannot use.
changed the title [-]WG: post the experimental/ext/agents reference implementation to agents-wg 20[/-][+]WG: review agents-wg PR 22 (agent discovery SEP) with experimental/ext/agents as a second implementation[/+]on Sep 17, 2026
Closing as overtaken: mcpkit adopted the SEP's identifier io.modelcontextprotocol/agents (#1541), ships examples/agents/discovery (#1540) and a conformance suite for agents-wg#22 (#1545). Any review comment still owed on agents-wg PR 22 gets a fresh, short ticket.
Activity
[-]WG: post the experimental/ext/agents reference implementation to agents-wg 20[/-][+]WG: review agents-wg PR 22 (agent discovery SEP) with experimental/ext/agents as a second implementation[/+]panyam commentedon Oct 16, 2026
Closing as overtaken: mcpkit adopted the SEP's identifier
io.modelcontextprotocol/agents(#1541), shipsexamples/agents/discovery(#1540) and a conformance suite for agents-wg#22 (#1545). Any review comment still owed on agents-wg PR 22 gets a fresh, short ticket.