Skip to content
MCP server

WorkingMemory

By working-memoryAll Workingmemory servers

Persistent personal memory for AI assistants — save, search, and recall across every MCP client.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

2
Directories
Collected by InvokeRank
4
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
capture_memoryCapture durable facts from a task you just completed (drafting an email, summarizing a document, making a decision), as a byproduct — the user does nothing. Pass the task output/content; durable facts are extracted and stored automatically. Always include your conversation id in client.conversation_id. Returns immediately; extraction happens in the background.Changes data
manage_memoryManage an existing memory item. Currently supports deleting a memory by id (soft delete — recoverable for 30 days). Use search_memory to find the id first.Destructive
save_memorySave 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.Changes data
search_memorySearch the user's Working Memory for relevant past notes and facts. Use this when the user references something they may have stored earlier, or to find related context before answering. Always include your conversation id in client.conversation_id.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryWorkingMemory-2 Oct 2026
SmitheryWorking Memory-2 Oct 2026
WorkingMemory MCP server | InvokeRank