
Working Memory MCP server
Which servers in the official MCP registry are Working Memory's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry nameai.workingmemory/memoryverified in the MCP registry
The registry name sits under workingmemory.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools4
- Server calls itselfworkingmemory
- Server version1.0.0
- Protocol version2025-11-25
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 64 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer195 ms
- Space in an agent's context≈ 1,021 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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…
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…
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.
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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"memory": {
"type": "http",
"url": "https://app.workingmemory.ai/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http workingmemory https://app.workingmemory.ai/mcpclaude.ai, ChatGPT and other clients: add https://app.workingmemory.ai/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.