MCP AutoMem

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/verygoodplugins-mcp-automem

About

Use cases: agent-memory

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

4 read · 6 write · 2 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

None found

Runs as

Node.js package

Tools (12)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• associate_memoriesAssociate Memories

  Description is built at runtime.

• automem_associate_memories

  Create a typed relationship between two memories.

• automem_check_health

  Check the AutoMem service health.

• automem_delete_memory

  Delete a stored AutoMem memory. Single-mode (set `memory_id`) or bulk-by-tag (set `tags`). Bulk-by-tag has no dry-run; verify with `automem_recall_memory({ tags, exhaustive: true })` first.

• automem_recall_memory

  Recall memories in one of three modes. (1) ID fetch: pass `memory_id`. (2) Tag enumeration: pass `tags` + `exhaustive: true` for paginated exact-match listing. (3) Ranked retrieval (default): hybrid search across vector/keyword/tags/recency, current-only by default server-side.

• automem_store_memory

  Store a durable memory in AutoMem. Single-mode (set `content`), supersede/correction mode (set `content` + `supersedes_memory_id`), or batch mode (set `memories: [...]`, up to 500). Batch mode does not accept per-item id/embedding/t_valid/t_invalid.

• automem_update_memory

  Update a stored AutoMem memory.

• check_database_healthCheck Database Healthread-only

  Check the health status of the AutoMem service and its connected databases (FalkorDB graph + Qdrant vectors). **When to use:** - Before a session to verify the memory service is available - When memory operations are failing unexpectedly - To check storage statistics **Example:** - check_database_health({})

• delete_memoryDelete Memorycan change or delete data

  Delete a memory by ID (`memory_id`) or bulk-delete by tag (`tags`). Use sparingly — consider `update_memory` instead. **Mode 1 — Single (default):** pass `memory_id` to delete one memory and its embedding. Idempotent: re-running on the same ID is a no-op. **Mode 2 — Bulk-by-tag:** pass `tags: [...]` to delete ALL memories tagged with ANY of these tags. Tag matching is exact (case-insensitive), any-of mode. There is NO dry-run. This can delete thousands of memories in one call. NOT idempotent in practice — re-running may catch new memories that were tagged the same way after the first call. V…

• recall_memoryRecall Memoryread-only

  Recall memories from AutoMem in one of three modes. The mode is selected by which params you pass. **Mode 1 — ID fetch:** pass `memory_id` to retrieve a single memory by ID. All other params are ignored. Routes to GET /memory/{id} and updates last_accessed. **Mode 2 — Tag enumeration:** pass `tags` + `exhaustive: true` for paginated exact-match listing (NOT ranked retrieval). Use this for cleanup/audit workflows where ranked retrieval silently undercounts large tag sets. Pair with `limit` (≤200) and `offset`. Returns `has_more`/`limit`/`offset` page metadata; next page at `next_offset`. Tag …

• store_memoryStore Memory

  Store memory in one of two modes — single-memory (set top-level `content`) or batch (set `memories: [...]` for up to 500). **Mode 1 — Single (default):** pass top-level `content` plus any optional fields (tags, importance, metadata, type, confidence, embedding, t_valid, t_invalid, etc.). **Mode 1b — Supersede/correct:** pass top-level `content` plus `supersedes_memory_id`. The server stores the replacement, marks the old memory invalid with `t_invalid=now`, merges supersede metadata, and associates old → new with `INVALIDATED_BY` (default) or `EVOLVED_INTO`. **Mode 2 — Batch:** pass `memori…

• update_memoryUpdate Memory

  Update an existing memory's content, tags, importance, or metadata. Use this to correct or enhance memories rather than storing duplicates. **When to use:** - To correct inaccurate information in a memory - To add tags that were forgotten - To adjust importance based on new understanding - To add metadata after the fact **Examples:** - update_memory({ memory_id: "8f3a2c1e-5b7d-4e9a-a1c3-2d4f6b8e0a91", importance: 0.95 }) // Increase importance - update_memory({ memory_id: "8f3a2c1e-5b7d-4e9a-a1c3-2d4f6b8e0a91", tags: ["project-x", "critical", "auth"] }) // Add tags - update_memory({ memory…

Compare and alternatives

Featured in

• Best MCP servers for vector search and databases

Signals

Stars

66

Forks

15

Open issues

12

Contributors

7

Last commit

Oct 22, 2026 (6 days ago)

Last release

Oct 20, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.verygoodplugins/mcp-automem

Version

0.10.0

Auth

Bearer token

Packages

npm @verygoodplugins/mcp-automem

License

MIT

Repository

github.com/verygoodplugins/mcp-automem

Website

automem.ai/?utm_source=mcp-registry

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql