All servers / Memory / agentmemory MCP server
agentmemory MCP server
Standalone MCP server for agentmemory — thin shim that re-exposes @agentmemory/agentmemory's MCP entrypoint
Tested by ConnectATDScore 94 out of 100. Tested 2026-11-18 on package version 0.9.33. Package: @agentmemory/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (33.9 seconds including download)
- Tools offered: 7
- Last published: 2026-11-09
- Weekly downloads (npm): 10,319
- License: Apache-2.0 · Direct dependencies: 1
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
memory_recall8 of 8 parameters describedSearch stored memories and session observations for relevant context. Use when you need to recall what happened in previous sessions, find past decisions, or look up how a file was modified before.
memory_save6 of 6 parameters describedExplicitly save an important insight, decision, or pattern to long-term memory.
memory_sessions4 of 4 parameters describedList recent sessions with status, observation counts, summaries and a continuation cursor. Filters apply before pagination; retain them when requesting the next page.
memory_smart_search7 of 7 parameters describedHybrid semantic+keyword search with progressive disclosure. Pass query to search, or expandIds to recover full results.
memory_export5 of 5 parameters describedExport memory data as JSON. Past the transport size limit the export is refused, so use the paging arguments on a large store.
memory_audit2 of 2 parameters describedView the audit trail of memory operations.
memory_governance_delete2 of 2 parameters describedDelete specific memories with audit trail.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.