Retrieve facts previously saved about THIS project and user: architectural decisions, naming conventions, pinned dependency versions, and stated preferences. Call this before answering questions about how the project is built, and before re-asking the user something they may have already told you. Returns ranked matches with an id and a relevance score. This searches the user's own stored memories only - to look up how MemorySync itself works, use memorysync_read_docs instead.

Persist one fact so it survives after this conversation ends: an architectural decision, a convention the user asked you to follow, or a constraint that will still be true next session. Call this when the user states a lasting preference or you settle a design question. Do not call it for transient chat, for content already returned by memorysync_search, or for anything a later session would be misled by. Save one discrete fact per call rather than a conversation summary.

Look up MemorySync's own public documentation: REST endpoints, SDK usage, MCP configuration, and integration guides. Call this before writing MemorySync integration code, so method names and parameters come from current docs rather than recall. Returns documentation text for the requested topic. This reads MemorySync product documentation only - to retrieve facts about the user's own project, use memorysync_search instead.

Fetch the complete stored record for a single memory id, including its text, tags, importance and timestamps. Use this after memorysync_search when a result looks relevant but the snippet is not enough to act on, or when you need the creation date to judge whether a fact is stale. Takes an id, not a search phrase - to find a memory by topic, call memorysync_search first and pass an id from its results.

Traverse the memory graph to return facts connected to a topic, so you can see the surrounding context rather than isolated matches. Use this when a decision depends on several linked facts - for example every memory touching authentication - or to discover related constraints you did not think to search for. memorysync_search ranks independent matches by relevance; this returns a connected neighbourhood instead.

Return memories that record decisions, along with any that contradict each other, so a superseded choice is visible rather than silently competing with the current one. Call this before proposing an architectural change, to check whether the question was already settled and why. This surfaces conflict between stored facts; memorysync_search returns matches without telling you when two of them disagree.

Permanently delete one or more memories by id. Use this when a stored fact is wrong or the user asks you to forget something - not to tidy up, because a deleted memory cannot be recovered. This previews by default: it reports what would be deleted and deletes nothing until dry_run is explicitly set to false. Confirm with the user before that second call. To find the ids to pass, use memorysync_search.