Resources
A resource is read-only data the server exposes to the client. Where tools do work, resources are addressable, cacheable documents — identified by URI and free of side-effects.
Discover resources
const { resources } = await client.listResources();
// → [{ uri: "mdmcp+data://session_id", name: "session_id", ... }]
Read a resource
const result = await client.readResource({ uri: "mdmcp+data://session_id" });
// result.contents[0] = { uri, mimeType, text } | { uri, mimeType, blob }
Available resources
mdmcp+data://session_id — the current MCP session ID. Diagnostic only;
useful when you're contacting support
and need to point EDITED at a specific session in the logs.
More resources will land as schemas are formalized — typically reference data the agent can read on demand (country code → region mappings, vertical taxonomies) without spending a tool call.
Resource or tool — which to use
| Use case | Pick |
|---|---|
| Searches, filters, anything parameterized | tool |
| Reference data the agent reads on demand | resource |
| Side-effectful operations | tool |
| Static documents the agent quotes verbatim | resource |
If in doubt: a tool is a verb (do something), a resource is a noun (read something).