Each call carries a scope — user, agent, app, run or session — so a single store can serve several assistants without their recollections bleeding into each other. get_memory_capabilities reports what the configured backend actually supports, so the calls that exist only against the cloud service announce themselves instead of failing mid-task.
A client for Mem0: 16 tools that write memories from text or messages, search them with a similarity threshold and topK, and manage the records afterwards — updates, deletions, ratings, event logs and exports.
- Memories stored from a block of text or from structured messages, with metadata and custom instructions, and either waited on or left to complete in the background
- Search by query with a similarity threshold, topK, filters, a reference date and optional reranking
- Every read and write scoped by userId, agentId, appId, runId or sessionId
- Listing with pagination, single records fetched by ID, updated and deleted
- Bulk text updates and bulk deletions across many memory IDs in one call
- A memory's audit trail and revision log
- Quality feedback recorded against a memory record with a reason
- Background processing events listed and fetched individually by event ID
- Export jobs started with a schema and instructions, then polled for status and download
- The features the configured storage-mode backend supports reported back on request
A Mem0 API key in MEM0_API_KEY and npx on your PATH. DEFAULT_USER_ID, DEFAULT_AGENT_ID and DEFAULT_APP_ID set the scope calls fall back to.
One command plus a key — npm install -g @pinkpixel/mem0-mcp, then supply credentials