/**
 * MCP resource: one saved memory by id, as `memory://item/{memory_id}`.
 *
 * Clients that support resources (Claude.ai connectors attach them through an
 * @-mention) can pull one specific memory into context. The ids are the `id:`
 * lines of memory_read and memory_list_recent results, so this is the "open
 * this memory" companion to the recall tools. There is no listing: the
 * template is advertised, and reading needs a known id.
 *
 * Moved here from the hosted connector (mnemoverse-mcp-remote,
 * src/resources/index.ts) in step 3c of the ADR-025 plan, with the same URI
 * template, name and output, so the connector can register this instead of
 * its copy. It returns only `memory_id`, `content` and `domain`: the engine's
 * point read also carries importance, valence, access counts and metadata,
 * which a model opening a memory does not need.
 *
 * Two limits, both the engine's. The point read looks only in the caller's
 * own store (GET /memory/atoms/{id} takes no domain), so a memory read from a
 * shared room cannot be opened here; the description says so. And a Vault
 * secret cannot be opened at all: the point read answers a secret's id with
 * 404, exactly as it answers an id that names nothing, so this resource
 * returns resource-not-found (-32002) for it, as for any missing memory.
 */
import { type McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { type MemoryToolDeps } from "./tools.js";
/**
 * Register the `memory://item/{memory_id}` resource on `server`. It reaches the
 * API only through `deps.apiFetch`, like the tools.
 */
export declare function registerMemoryResources(server: McpServer, deps: MemoryToolDeps): void;