mm_remember

Store an enriched memory note in local semantic memory so a future session can recall it by meaning. Embeds the content with a bundled local model (offline and private — data never leaves the machine) and persists it under .mm/index/amem/. YOU supply the enrichment (summary, tags, keywords, links) in-session; the server makes no LLM calls and only embeds the content and persists what you give it, so skipping enrichment loses most of the recall value. Remember durable, non-obvious knowledge — a decision and its reasoning, a completed spec, a gotcha — not transient/trivial state. Idempotent on a stable id (explicit id, else source:source_ref, else a content hash): re-remembering the same id updates that record in place, so reuse ids to evolve a memory instead of duplicating it. Call mm_recall first to find related note ids for links and to avoid duplicates. Fail-soft: if the model or store is unavailable it returns an error result without breaking other tools. See docs/memory-enrichment-contract.md.

At a Glance

• Category: Plugin Management
• Source: Built-in
• Required parameters: 2
• Total parameters: 9

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root (directory containing .mm)
content	string	Yes	The memory itself, in self-contained prose — this is what gets embedded, so it must carry the actual substance (include the why, not just the what).
summary	string	No	One-line, recall-optimized summary shown verbatim in recall results; front-load the subject and the decision/finding. You supply this.
tags	array of string	No	A small set (~2-5) of stable, reusable kebab-case facet labels for filtering recall; reuse existing tags rather than coining near-duplicates. You supply these.
keywords	array of string	No	Alternate phrasings/synonyms a future query might use that do NOT appear in content, to widen semantic recall. You supply these.
links	array of string	No	Stable ids of related memory records; call mm_recall first to discover them, then pass those ids — do not guess. You supply these.
source	string	No	Origin of the memory — e.g. “spec” | “session” | “note” | “issue” or a free string (default: “note”)
source_ref	string	No	Opaque pointer back to the origin within its source (e.g. a spec slug, a session id)
id	string	No	Explicit stable id; you own idempotency. If omitted, derives from source:source_ref (both present) else a content hash. Re-remembering the same id updates the record in place (upsert) — reuse it to evolve a memory.

Example

{
  "tool": "mm_remember",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "content": "A brief description of the item",
    "summary": "example-summary",
    "tags": [
      "example-tag"
    ]
  }
}

Related Tools

• mm_list_plugins - [DEPRECATED — use mm_list with entity=plugin] List all loaded plugins with th…
• mm_get_plugin_info - [DEPRECATED — use mm_get with entity=plugin] Get detailed information about a…
• mm_push_team_checkin - Push a team check-in to the cloud. Scans local specs and features, captures c…
• mm_fetch_team_checkins - Fetch all team members’ check-ins from the cloud. Returns display names, bran…
• mm_claim_spec - Claim a spec from a teammate. Records the claim in the cloud (first-claim-win…