mcp server
WorkingMemory
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Description as published by the maintainer. Source
- version 1.0.0
- active
- retrieval
- memory and context
active — Registry entry last updated 2026-07-17. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
capture_memory(client, task_content, task_description)- Capture 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. Required: task_content.
manage_memory(id, action)- Manage 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. Required: action, id.
save_memory(text, client)- 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. Required: text.
search_memory(k, query, client, dedupe_recent, conversation_id)- Search 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. Required: query.
Last successful function declaration observed on . Source: https://app.workingmemory.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://app.workingmemory.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-17 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-17 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | app.workingmemory.ai | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | app.workingmemory.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json