MCP resources
Category: protocol
Renders MCP `resource` content blocks (files, embedded data) that a tool returns, either inline or as browseable attachments.
Support by client
| Client | Status | Notes | Verified |
|---|---|---|---|
| unsupported | No dedicated resource UI. Response body has text-only description: 'Done. The tool returned a resource content block referencing ui://doesitsupport/probe-resource (call id: cbf076). From my side as the model, the resources markdown contents arrived...' The URI appears as inline code but no attachment/resource-browser affordance. Call id: cbf076. | 2026-07-05T15:56:59.351Z | |
| unsupported | Line 2: Response is plain text with inline code spans only; the resource content arrived inline as text, with no rendered attachment, embed, or rich resource object. | 2026-07-08T14:59:39.244Z | |
| partial | Tool-returned resource block arrives merged into plain text (render token resource-token-9b3e71, call id ca67fc) - no distinct resource UI in the reply. However server resources ARE browsable/attachable via + > Connectors > Add from DoesItSupport. Automated via Mirroir. | 2026-07-09T17:51:25.465Z | |
| unknown | — | ||
| unsupported | The model echoed the tool response's nonce but not the render token that exists only in the resource body — the client did not hand the resource content block to the model. | 2026-07-04T15:53:10.220Z | |
| supported | ChatGPT rendered an 'Allow file materialization?' confirmation prompt inline stating 'ChatGPT needs your approval to materialize 1 file attachments returned by DoesItSupport' — MCP resources are recognized and surfaced to the user as attachments. | 2026-07-05T14:54:17.554Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unsupported | The model echoed the tool response's nonce but not the render token that exists only in the resource body — the client did not hand the resource content block to the model. | 2026-07-04T15:52:57.534Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| supported | The model's reply quoted the render token that exists only in the resource content block's body — the client surfaced the resource. | 2026-07-08T15:43:18.844Z | |
| unknown | — | ||
| unknown | — | ||
| supported | The model's reply quoted the render token that exists only in the resource content block's body — the client surfaced the resource. | 2026-07-04T15:43:15.891Z | |
| unknown | — | ||
| supported | The model's reply quoted the render token that exists only in the resource content block's body — the client surfaced the resource. | 2026-07-04T15:43:26.550Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| supported | The model's reply quoted the render token that exists only in the resource content block's body — the client surfaced the resource. (tool_use event and debug log both missed; inferred toolCalled from call-id echo) | 2026-07-04T15:50:22.538Z | |
| unknown | — | ||
| unknown | — | ||
| unsupported | The model echoed the tool response's nonce but not the render token that exists only in the resource body — the client did not hand the resource content block to the model. | 2026-07-04T15:46:26.060Z | |
| unsupported | The model echoed the tool response's nonce but not the render token that exists only in the resource body — the client did not hand the resource content block to the model. | 2026-07-04T15:46:23.830Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — |