Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://app.workingmemory.ai/mcp4 tools · 515mssave_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…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…
| Parameter | Type | Description |
|---|---|---|
| text* | string | The thought or note to save. |
| client | object | Optional context about the originating client session. Helps users later find saves from a specific conversation. `conversation_id` groups multiple saves; `con… |
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.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.
| Parameter | Type | Description |
|---|---|---|
| query* | string | Semantic query. |
| k | number | Max results (1–20). Defaults to a sensible value. |
| conversation_id | string | Optional. Restrict results to notes stamped with this conversation_id at save_memory time. Empty / whitespace-only values are treated as absent. |
| dedupe_recent | boolean | Optional. When false, semantic matches that are also recent are still returned in `relevant` (raw semantic results rather than RAG-deduped). Defaults to true. |
| client | object | Context about the CURRENT client session. Pass your conversation/thread id as `conversation_id` — it identifies this session for cross-session memory instrumen… |
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.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.
| Parameter | Type | Description |
|---|---|---|
| action* | string | The management action to perform. |
| id* | string | The memory item id to act on. |
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…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…
| Parameter | Type | Description |
|---|---|---|
| task_content* | string | The task output/content to mine for durable facts (max 32KB). |
| task_description | string | Optional one-line description of the task, as extraction framing. |
| client | object | Current client session context. Pass your conversation/thread id as conversation_id. |
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.