Reference

remember

Write durable memory only after capture policy, scope, and secret-redaction boundaries are satisfied.

Confirm the write landed

Read the memory back through a scoped search rather than trusting the write response alone.

search_memory({
  query: "OAuth for hosted ChatGPT connections",
  limit: 3
})

Public MCP tool

remember

Purpose

Persist durable information that an approved agent should be able to recall later. This is the direct durable-write API; event streams should pass through capture policy before calling it.

When to use

A user explicitly asks to save a durable fact, preference, decision, or vetted handoff note.
The information will still be useful after the current chat or task ends.
The caller can supply the owning path and an authorized project, scope, or team boundary.

When NOT to use

Do not store transient chat instructions, a one-off answer, or raw high-volume tool output.
Do not persist passwords, bearer tokens, API keys, or private-key material; redact or reject secrets first.
Do not use generic memory for financial records; use ledger for transactions and reminders.
The REST API accepts a wider field set than the public MCP tool; see https://xmemo.dev/docs/api/memory for scope, bucket, team and provenance filters.

Required scope

memory:write is required for the public MCP write surface.
The authenticated owner must be allowed to write the resolved path/scope; team writes also require team membership.

Parameters

Name	Type	Description
`content`	string · required	Durable memory body. Keep it factual, bounded, and free of secrets.
`path`	string · required	Logical location used to attach the memory to a project or durable namespace.
`create_project`	boolean · default: false	Generic public profile only: create the owning project if the path implies one. Not accepted on the ChatGPT or Claude plugin profiles.

Return schema

Success text includes the stored memory reference/ID, logical path, writer identity, account, and device label. Public clients should treat the reference as an opaque identifier.

Examples

Save an explicit durable decision

remember({
  content: "Use OAuth for hosted ChatGPT connections.",
  path: "projects/memory-os/decisions"
})

Errors

401/403: the MCP token is missing or does not include memory:write.
Validation failure: content or path is empty, malformed JSON is supplied, or a value violates the storage contract.
Authorization failure: the caller cannot write the requested scope, project, or team.
Safety rejection: secret-like content or reserved identity metadata is blocked or sanitized.

recall — Fetch a few relevant memories after storing a durable fact.
recall_context — Build a bounded context pack before a later task.
ledger — Store governed financial records instead of generic memory.

Source: MCP tool surface