Read and discover
Call currentMemoryStore to verify the selected store and role. listMemoryStores discovers stores you can access. getMemoryPolicy reads the selected store’s policy. listMemories browses saved records, while recallMemory performs semantic search. The example below shows a tool name and arguments, not a complete HTTP request.
{
"name": "recallMemory",
"arguments": {
"query": "Project architecture decisions",
"limit": 10
}
}| Tool | Purpose |
|---|---|
currentMemoryStore | Selected store, role and recording identity |
listMemoryStores | Stores accessible to this account |
getMemoryPolicy | Selected store policy |
listMemories | Browse stored memories |
recallMemory | Semantic retrieval; query up to 4,000 characters, limit 1–50 (default 10) |
Create, update and delete
Use createMemory for a new fact, updateMemory when an existing fact changes, and deleteMemory to remove a known record. Search before creating to avoid duplicates. Memory content is limited to 4,000 characters, and a create request can reference up to 32 existing related-memory UUIDs. Do not supply an account or store ID: the server derives them from the authenticated connection.
{
"name": "createMemory",
"arguments": {
"content": "The project uses PostgreSQL for persistent storage."
}
}Work with relationships
suggestMemoryLinks finds potential relationships. updateMemoryLink changes a relationship and adjustMemoryLinkStrength adjusts its strength. Use UUIDs from actual results. Hosted memory uses the dashboard for its graph; the local plugin’s openMemoryGraph tool is not exposed by the cloud MCP server.