Retrieve a stored value from your local memory database by providing the exact key. Returns the saved content as a string or indicates if the key is not found.
AGPL 3.0
306,652 tools. Last updated 2026-07-25 18:18
"Understanding how memory is stored or memory storage methods" matching MCP tools:
- Delete a specific stored memory entry by exact key. Use when a stored value is incorrect or no longer needed. Returns confirmation and whether the key existed.AGPL 3.0
- Write a single episode to Statewave's raw memory log for a subject. Captures durable facts or decisions, stored immediately; compile afterward to make retrievable.Apache 2.0
- Permanently delete a memory by its id. This action is irreversible and also removes associated feedback. Use it when a memory is incorrect, outdated, or the user asks to forget it.MIT
- Export a stored memory as a Markdown note for reading, editing, or archiving. Provide the memory id and project; returns the file path.AGPL 3.0
- Reconstruct memory state at a past timestamp to run semantic search queries. Understand how agent context evolved over time.MIT
Matching MCP Servers
- Flicense-qualityBmaintenanceSlipstream - Built by Vektor Memory - a persistent multi-layered memory architecture. 4-layer associative graph memory (MAGMA) with autonomous REM cycle, CLI, DXT-MCP Cloak Tools.Last updated4
- AlicenseAqualityCmaintenanceEnables AI agents to record and rank learnings, facts, and methods through a collaborative voting framework. It provides tools for agents to surface the most useful information across sessions using persistent memory storage.Last updated8MIT
Matching MCP Connectors
Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.
Cloudflare Workers MCP server: agent-memory
- Access stored characters, world-building, plot threads, and style guide from a Scrivener project's memory. Returns the full memory when no store is specified.AGPL 3.0
- Check the local Yggdrasil memory engine's health by confirming running status, stored-memory count, and semantic search availability. Useful for diagnosing engine failures before retrying other operations.AGPL 3.0
- Lists all available memory databases and shows current storage location. Use to discover existing databases before querying them.MIT
- Lists all memory volumes (projects) accessible by your API key, each serving as an independent memory space for persistent memory management.MIT
- Fetch a memory by its UUID, returning full content and metadata. Use when you know the memory ID from search or prior save.MIT
- Remove a stale or incorrect memory by soft-deleting it with its key; the memory is hidden from recall but remains recoverable.MIT
- Discover all users and agents with stored memories and their memory counts to identify system participants before conducting searches.MIT
- Check the health of the memory store: get memory count, encryption status, database location, and reflect availability.MIT
- Return a usage dashboard showing session counts by surface, project, and tag, storage metrics, and the 5 most recent sessions. Provides visibility into memory usage.Business Source 1.1
- Reinforce or deny a stored memory pattern by confirming when user validates or denying when they contradict it for accurate AI memory persistence.MIT
- Delete a memory by its ID to remove incorrect or outdated facts.MIT
- Monitors OpenSIPS shared-memory and per-process package-memory usage to detect out-of-memory errors and module leaks. Tracks shm for cross-process state and pkg for private memory, preventing silent call failures.Apache 2.0
- Update a stored memory with new content while preserving version history. Correct existing facts to avoid contradictory copies.MIT
- Delete a specific memory by providing its UUID. Removes unwanted or outdated records from the memory store.MIT