Resources (deferred, post-GA)#
MCP resources are not implemented in v1.list_resourcesandread_resourceare explicitly deferred to post-GA. v1 ships tools only (list_tools/call_tool). Nothing in the v1 integration path depends on resources. This page documents the deferral so the gap is on record — it is not a live feature.
The MCP protocol's resources primitives (list_resources / read_resource, and optionally subscribe) expose brand-scoped, read-only data as first-class addressable resources (URIs, MIME types) rather than via call_tool. qaqnuz has not shipped these in v1.
Candidate surfaces (future, not live)#
If and when resources are introduced, these are the candidate read-only surfaces under consideration. None of these is callable today — they are listed only to describe the intended future shape.
| Candidate surface | Illustrative URI pattern |
|---|---|
| Conversation history | qaqnuz://brand/{brandId}/conversations/{id} |
| Agent version catalogue | qaqnuz://brand/{brandId}/agent-versions |
| Tool definitions (brand view) | qaqnuz://brand/{brandId}/tools |
| Runtime traces / audit log | qaqnuz://brand/{brandId}/traces/{traceId} |
| Learning suggestions | qaqnuz://brand/{brandId}/learnings/suggestions |
All candidates are purely read-only and would bind to the same brand + scope + per-key model as tools — no new authorization path.
Why deferred#
Resources are deferred past GA for several independent reasons:
- Tools are the GA commitment. The v1 contract is
list_tools/call_tool;
resources are additive and not needed by the launch use case.
- Scope-binding is an open design question. How a resource URI maps to a
<resource>.<action> scope (without violating the no-wildcard rule), and how a subscription is classified, are unresolved.
- No versioned resource schema exists yet. Publishing an unstable resource
schema would create a 6-month deprecation obligation prematurely.
- Subscriptions need a stateful transport.
subscriberequires a server-push
channel (SSE/WebSocket), which depends on the public HTTP gateway that is itself deferred.
When resources could ship#
Resources become a build item only when all of the following are true:
- The public HTTP/SSE gateway is live (it is not yet).
- A resource scope-binding design has been security-reviewed.
- At least two candidate surfaces have a versioned, typed schema.
- The security test suite covers resource-enumeration attacks.
Until all four hold, list_resources and read_resource are not implemented, and the list_tools / call_tool surface is unaffected.
What to do today#
Use tools for everything. If you need read access to brand data, look for a read-side-effect tool in your list_tools response and call it via call_tool. Do not build against resource URIs — they do not resolve in v1.