Search all remembered facts by content, across every project scope.

The default entry point. Use it before assuming something is not known: it searches EVERY scope at once, so there is no need to guess which project a fact was recorded under. Use memory_get instead when you already know the exact scope and name, memory_list to browse without a query, and memory_recent for what changed lately.

Two layers, blended by default:

• Lexical (FTS5): multi-word queries first require ALL terms in one entry, then fall back to ANY term (ranked by how many match), so one non-verbatim word doesn't zero the result.

• Semantic (if embeddings are present): vector nearest neighbours on a multilingual sentence model, which finds entries about the same idea even with no shared keywords.

Read-only. Archived entries are never returned. Returns a list of entries, best match first; an empty list when nothing matches or the query is invalid.

Report whether semantic search is active, which embedding model is used, and how many entries have a current vector embedding.

Use it to understand why memory_search finds (or misses) entries that share no keywords with the query: entries without a current embedding are lexical-only until the next embed-backfill run (a CLI command, not an MCP tool). For general counts use memory_stats; to test that the store works, memory_healthcheck. Read-only, takes no arguments.

List the most recently created or updated memory entries, newest first.

Use it to catch up on what changed lately (start of a session, after another agent worked), optionally within one scope. To find entries by content use memory_search; to browse a scope or type without time ordering use memory_list; for who changed what, use memory_events. Read-only.

Fetch one memory entry, complete, by its exact scope and name.

Use it when you already know both keys (from memory_search, memory_list or memory_recent results) and need the full, current content before relying on it. Returns null when no entry has that scope and name, or when it is archived and include_archived is false. Read-only.

Browse entries by scope, type and archived state, WITHOUT a search query.

Use it to see everything in a project scope (onboarding to a codebase), every entry of one type (e.g. all feedback), or what has been archived (candidates for memory_restore). To find entries by content use memory_search; for the latest changes, memory_recent. Read-only. An invalid type returns [{"error": ...}].

Read the append-only audit log, newest first: who wrote, updated, archived or restored what, when, from which client, and any conflicts or secret redactions.

Use it to answer "who changed this, and why?". To see the previous CONTENT of an entry, use memory_history instead; for the latest entries themselves, memory_recent. Read-only and available on any connection; scope-locked connections only see their own scope's events.

List every known project/topic scope with its number of entries.

Use it first to discover valid scope values for the other tools, or to see which projects have memory at all. For the total count and the database location use memory_stats; to browse the entries of one scope, memory_list. Read-only, takes no arguments. A scope-locked connection only sees its own scope.

Report the total number of entries, the number of archived entries, the database file location and the list of scopes.

Use it for a quick overview or to check which database file this connection uses. For per-scope counts use memory_scopes; for semantic search coverage, memory_embed_status; to verify the store actually works, memory_healthcheck. Read-only, takes no arguments.

Show the prior versions of one entry that were overwritten or deleted, newest first.

Every write that replaces an entry keeps the previous version automatically, so nothing is silently lost even if another agent overwrote it. Use it to recover or compare earlier content. For who made each change use memory_events; for the current version, memory_get. Read-only, available even on a read-only connection. Returns an empty list when the entry has no prior versions.

Record a new fact, or update an existing one (same scope + name updates it in place).

Search first (memory_search) to avoid creating a duplicate under a different name. An update keeps the previous version in memory_history and is logged in memory_events, so it can be undone. Updating an archived entry is refused: restore it first with memory_restore. Secret-shaped values in content (API keys, tokens, password: ... lines) are replaced by [REDACTED] before storage; if any were, the result includes "redacted": [<codes>].

Returns {"ok": true, "id": ...} on success, or {"ok": false, "error": ...} for an invalid argument, a conflict (stale expected_updated_at or archived entry) or a busy database (retry). Not available on read-only connections.

Archive (soft-delete) one entry: hide it from normal reads and search while keeping it, restorable with memory_restore and audited in memory_events.

Use it for a fact that became wrong or obsolete; to correct a fact, prefer memory_write on the same scope + name. Nothing is ever physically deleted. Returns {"ok": true} if the entry is now archived (also when it already was), {"ok": false} if no entry has that scope and name, or {"ok": false, "error": ...} when the reason is empty. Not available on read-only connections.

Restore one archived entry so it appears again in normal reads and search. The inverse of memory_archive.

Find archived entries with memory_list(archived=true). The restore is logged in memory_events with your reason. Returns {"ok": true} if the entry is now active (also when it was not archived), {"ok": false} if no entry has that scope and name, or {"ok": false, "error": ...} when the reason is empty. Not available on read-only connections.

Self-test MemCore end to end (about 1 s): write, read, search (strict AND and OR-fallback modes), history and delete.

Use it instead of assuming a connection is healthy just because it is listed: a connection can look fine while search silently misbehaves. The test only writes to a throwaway scope (_healthcheck, or _healthcheck_<scope> on a scope-locked connection) and always cleans up; real entries are never touched. Returns {ok, checks[], db_path}. Not available on read-only connections; use memory_stats there.