Align capability key to SEP-2133 extensions format (#25)
Both SDKs now use Capabilities.Extensions with key "io.modelcontextprotocol/interceptors". Previously C# used the short key "interceptors" and Go used Capabilities.Experimental. SEP capability example updated to match. https://modelcontextprotocol.io/seps/2133-extensions --------- Signed-off-by: Ukjae Jeong <jeongukjae@gmail.com>
This commit is contained in:
parent
725d22fd28
commit
99bc7c9bb0
2 changed files with 20 additions and 19 deletions
|
|
@ -24,7 +24,7 @@ Status of this Go SDK implementation against the SEP-2624 interceptor proposal.
|
|||
| Audit mode | `ModeAudit` records results without blocking; mutated payloads not propagated |
|
||||
| Timeout & context | Per-interceptor timeouts via `InvokeParams.TimeoutMs`, chain-level context cancellation, `InvocationContext` with principal/traceId |
|
||||
| Receiving direction (client → server) | All server-side method calls intercepted via `AddReceivingMiddleware` |
|
||||
| Capability declaration | Interceptor metadata injected into `initialize` response via `Capabilities.Experimental` |
|
||||
| Capability declaration | Interceptor metadata injected into `initialize` response via `Capabilities.Extensions` |
|
||||
| First-party (in-process) deployment | `Server.LocalChain()` creates an in-memory transport `chain.Chain`; interceptors invoked via JSON-RPC even in-process |
|
||||
| Third-party and hybrid deployment | Chain entries can point to any `*mcp.ClientSession` — local (in-memory), stdio, or HTTP transport |
|
||||
| `json.RawMessage` payloads | Interceptor handlers receive `json.RawMessage` via `interceptor/invoke`, matching the SEP's JSON-level payload model |
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ behavior as remote interceptor servers.
|
|||
|
||||
During initialization, a lightweight middleware intercepts the `"initialize"`
|
||||
response and injects interceptor metadata into
|
||||
`Capabilities.Experimental["io.modelcontextprotocol/interceptors"]`. This
|
||||
`Capabilities.Extensions["io.modelcontextprotocol/interceptors"]`. This
|
||||
follows the same pattern as the variants extension
|
||||
(`io.modelcontextprotocol/server-variants`).
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue