MCP tool
save_memory
save_memory is a tool name used by 2 different MCP servers. They are not necessarily the same tool — here is what each one does.
2 MCP servers expose a save_memory tool: OwnMemory and WorkingMemory. Their input schemas differ, so compare them below before picking one.
Servers exposing save_memory
From the publisher:Saves one fact, after the hard rules allow it; points out facts already saved, even when worded differently
Install OwnMemory →From the publisher:Save a thought, insight, fact, or todo to the user's Working Memory. The text is parsed and stored as one or more structured memory items, searchable a moment later via search_memory. Also use this when the user pastes memories or notes brought from another assistant — pass the full pasted text; it is split into individual memories automatically.
Install WorkingMemory →Parameter Type Description text*string The thought or note to save. clientobject Optional context about the originating client session. Helps users later find saves from a specific conversation. `conversation_id` groups multiple saves; `conversation_title` is human-readable.
Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.