List recent packets on the configured ltm server. Returns a table with ID, creation time, and goal.

Fetch a packet by ID and return a human-readable summary (goal, constraints, decisions, attempts, next step).

Fetch a packet by ID and return the raw JSON document. Use when you need the full v0.2 packet — otherwise prefer 'show' or 'resume'.

Render a prompt-ready resume block for a packet so the current agent can continue prior work. Output is markdown intended to be treated as authoritative context.

Send a Core Memory Packet to the configured ltm server. The packet is schema-validated and scanned for secrets/absolute paths before upload. Pass the packet as a JSON object under 'packet'. Use 'ltm example' via the 'example' tool if you need a valid shape reference.

Save the current session as a Core Memory Packet. Build the packet JSON from the active conversation — goal, locked decisions, failed attempts, open questions, next step — and pass it as 'packet'. Same validation and redaction as 'push'; use this when the intent is 'persist my session' rather than 'ship a pre-built packet'.

Delete a packet by ID from the server. Destructive — confirm with the user before calling.

Publish a packet to a public URL anyone can view (no account required) and copy as a prompt. The URL is unguessable (it embeds the packet's ULID). Returns the public URL. Idempotent — re-publishing a published packet preserves the original URL and timestamp. Confirm with the user before calling: this makes the packet content world-readable.

Revoke public access to a previously published packet. The packet itself is not deleted — only the public URL stops working.

Return an embedded sample v0.2 Core Memory Packet. Useful as a shape reference before calling 'push'. No server round-trip.

Report the configured ltm host and a short fingerprint of the stored token. Use to verify the server the MCP will hit before pushing.

Return the URL of the managed ltm platform's web dashboard so the agent can surface it to the user. Errors when the user is configured against a self-hosted server. No server round-trip.