delete_memory
Permanent. There is no undo. Retrieve the memory with get_memory first if you need to verify what you’re deleting.
Parameters #
| Parameter | Type | Required | Description |
|---|---|---|---|
memory_id | number | Yes | The ID of the memory to delete |
Examples #
# Delete a specific memory
delete_memory(memory_id: 42)
Power Combinations #
Source correction — Memory MCP intentionally does not allow source to be modified after storage (source is provenance, not a tag). If a memory was stored with incorrect source attribution, the correct approach is to re-store it cleanly and delete the original:
# 1. Retrieve the incorrectly sourced memory
get_memory(memory_id: 101)
# 2. Re-store with correct source attribution
store_memory(
content: "...",
labels: "...",
source: "correct-source/agent-name"
)
# 3. Delete the original
delete_memory(memory_id: 101)
Curated collection cleanup — when pruning a hand-maintained memory set (user profiles, reference docs, pinned context), delete the old version before or after storing the updated one to avoid duplicates surfacing in retrieval.
memory_stats can help identify memories by source or label before bulk cleanup — use it to confirm what you’re targeting before deleting.