Compatibility Report
Generated from the MCP Gateway client conformance harness
This report summarizes the unattended client compatibility run for the public MCP Gateway contract. A capability is marked supported only when the conformance harness exercises it through that client's public automation path. Unsupported entries include a reason instead of implying success.
Client matrix
| Client | Tools | Resources | Updates | Cancellation | Logging | Completions | Structured errors |
|---|---|---|---|---|---|---|---|
| MCP TypeScript SDK reference | Pass | Pass | Pass | Pass | Pass | Pass | Pass |
| MCP Inspector CLI | Pass | Pass | Not exposed through unattended CLI path | Not exposed through unattended CLI path | Not exposed through unattended CLI path | Not exposed through unattended CLI path | Not exposed through unattended CLI path |
| Lovelace legacy HTTP MCP client | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation | Not compatible with Streamable HTTP session negotiation |
Capability coverage
The report model includes authorization discovery, client identity, resource-bound tokens, tools, resources, updates, cancellation, sampling, elicitation, roots, prompts, completions, logging, and structured errors. Client-specific rows show pass or unsupported for each capability. Unsupported means the current unattended client path cannot exercise that capability with a bounded, deterministic run.
Authorization discovery, client identity, and resource-bound token behavior are verified by the gateway conformance suite and reported as client-specific coverage where a client path exposes those flows.
Refresh process
The compatibility report is generated from the same gateway conformance harness used in regression testing. To refresh it, run the MCP Gateway client conformance workflow and update this page from the generated per-client feature results. Do not edit support status by hand without the corresponding conformance result.