memai-memorylisted

How to use the MemAI MCP server (long-term agent memory: one ACID SQLite store, BM25 keyword search) — which tool family to call when: pulse/search/recall/list_by_domain/list_recent/ list_domains/get_memory/help to read; note, reasoning, anti_pattern, checkpoint, handoff, diagram to write; diagram_*/get_diagram for flows; edit_memory/link_memories/set_confidence/also_domain/forget/purge_memory to curate — plus the session/domain/tags convention, with domains as nested PATHS and cross-listing (also), and review_after/source_ref for a memory that will go stale. Use at the START of a session or when RESUMING work (warming a cold session), whenever SAVING or LOOKING UP durable knowledge (a fact, a decision, a rule, a pitfall), when DOCUMENTING a routine as a flow, and before PAUSING or ENDING work (checkpoint). Also on "MemAI", "memory", "long-term memory", "warm up the session", "checkpoint", "what did the last session leave", "save this lesson", "anti-pattern", "diagram of the flow".
Filipe-Soares-de-Almeida/MemAI · ★ 0 · AI & Automation · score 70

Install: claude install-skill Filipe-Soares-de-Almeida/MemAI

# memai-memory — using the MemAI MCP server **MemAI** is a long-term memory store with **BM25 keyword** retrieval, exposed over MCP under the name the host registered the server with — `mcp__memai__*` for the documented one. It matches on the **words that were written** — an exact identifier (`F100_TOTAL`, `USE_NEW_PARSER`, `proj-1042`) as readily as a phrase — which is why `tags` carry the synonyms a body never happened to use. > **`help()` is the source of truth for the tools.** `help()` lists every tool > with a one-line summary; `help(command='<name>')` returns that tool's > **signature and full documentation**, read live from the code, so it cannot > drift from behaviour. When unsure of a name or an argument, call `help` > instead of trusting this file. > **Not every tool is loaded.** `MEMAI_TOOLS` names the tool groups a process > publishes (`core`, `diagrams`, `curation`; `full` is the default), because > every published schema is paid for on every request. A tool this file names > may therefore be absent from the session. `help()` documents all of them > regardless and reports the ones this process did not load, under > `not_loaded` — so an unavailable tool is a setting to change, not a missing > feature. > **Transport:** a local **stdio** process (`memai-mcp`), no HTTP server. Only > the agent talks to it over MCP. The `memai-hook` CLI opens the same SQLite > file directly, without MCP, which is how the store reaches a session before > any tool has loaded (see [§