Memory MCP server

Read from the package source without running it. The installed server may list more.

• memory_cleanup

  Clean up stale memories. Archives completed TODOs and optionally removes old low-importance memories that haven't been accessed. Keeps the memory store lean and relevant.

• memory_deletewrite action

  Remove a memory that is no longer relevant or was stored incorrectly.

• memory_export

  Export all memories for the current project as JSON. Use for backup, migration, or sharing project context with team members.

• memory_import

  Import memories from a JSON array. Use to restore from backup, migrate between machines, or bootstrap a project with shared team context.

• memory_init

  Initialize project context. Auto-called on server startup \u2014 only call manually if switching projects mid-session. Returns conventions, recent decisions, open TODOs, and project metadata.

• memory_list_projects

  List all projects that have stored memories, with memory counts and last session dates.

• memory_search

  Search past memories by meaning. Use this BEFORE starting work to check if there's existing context about a topic. Also use when you're unsure about a convention, past decision, or known bug.

• memory_session_end

  Save a session summary before ending. Captures what was accomplished and what's left to do. This creates continuity \u2014 the next session picks up exactly where this one left off.

• memory_status

  Manage TODO status. Update a todo's status (pending \u2192 in_progress \u2192 done) or list todos by status. Essential for tracking work across sessions without external files.

• memory_store

  Save important information to persistent memory. ALWAYS use this when you: make an architectural decision, discover a bug or gotcha, establish a convention, learn a user preference, identify a TODO, or gain important project context. These memories persist across sessions and help future you work faster. MANDATORY \u2014 call this tool immediately when any trigger fires. Do not batch or defer. Whe

• memory_updatewrite action

  Update an existing memory when information changes. Use when a decision is revised, a bug is fixed, or a convention evolves.

• Code scan4 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 203 days ago4/15
• Maintainer identityregistry namespace matches repository owner6/10

Memory: common questions

Is Memory MCP server safe?

Mostly: it is graded B (72/100). Read the Memory safety report

How do I install Memory?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Memory need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Memory maintained?

The last commit was 218 days ago (2026-03-09). The latest release is v0.5.2.

What can I use instead of Memory?

Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Knowl MCP server. Compare all Memory alternatives.