Memstack MCP server

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

• memory_compile_context

  Compile memories into an LLM-ready system prompt (markdown formatted, token-budgeted, split into important and recent sections).

• memory_deletewrite action

  Delete a single memory by ID.

• memory_delete_manywrite action

  Delete multiple memories by ID in one call. Returns the number actually deleted.

• memory_dry_run_prunewrite action

  Preview what would be pruned by a given strategy WITHOUT actually deleting. Scoped to a single actor \u2014 defaults to the current session actor. Returns the memory IDs that would be removed.

• memory_export

  Export a snapshot of memories for backup or migration. Returns { version, memories, exportedAt }.

• memory_get

  Get a single memory by ID. Returns null if not found.

• memory_health

  Check the health of storage, LLM, and embedding connections.

• memory_import

  Import memories from a snapshot previously produced by memory_export. Restores each memory as-is, including its original ID.

• memory_merge

  Merge multiple memories into one. Uses the highest-importance memory as the base and appends content from the rest.

• memory_process

  Store a memory with auto-enrichment (importance scoring, tag extraction, auto-summarization, auto-pruning). This is the primary method for recording interactions.

• memory_prune

  Prune (delete) memories matching the given strategy. Scoped to a single actor \u2014 defaults to the current session actor. Returns the pruned memory IDs and count. Handle with care.

• memory_purge_actorwrite action

  Delete ALL memories belonging to a specific actor. Irreversible.

• memory_retrieve

  Retrieve memories for an actor with optional filtering, semantic search, and date range constraints.

• memory_stats

  Get memory statistics: total count, by type, by actor, average importance, and more.

• memory_store

  Store a memory directly without enrichment. Use this when you already have importance/tags or want precise control.

• memory_store_batch

  Store multiple memories in one call, directly without enrichment. Embeddings (if configured) are computed in a single batched call for efficiency.

• memory_summarize

  Summarize old memories into a single summary memory. Compresses N interactions into 1 summary via LLM.

• memory_touch

  Bump a memory's recency (last-accessed timestamp) without changing its content, id, or createdAt.

• Code scan5 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 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Memstack: common questions

Is Memstack MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Memstack safety report

How do I install Memstack?

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

Does Memstack need an API key?

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

Is Memstack maintained?

The last commit was in the last day (2026-09-20). The latest release is v0.7.2.

What can I use instead of Memstack?

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