A side-by-side look at the Recallnest and Total Agent Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Recallnest for knowledge & memory work as a local process; choose Total Agent Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Recallnest when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
Total Agent Memory tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Recallnest is categorized under Knowledge & Memory and uses a local stdio subprocess. Total Agent Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Recallnest for knowledge & memory work and Total Agent Memory for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Recallnest is listed as free. Auth: api key required. Total Agent Memory has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aliceljy-recallnest and total-agent-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Recallnest has a quality signal of 59/100 (Good) with 3 views, 0 installs and 15 GitHub stars. Total Agent Memory has 44/100 (Fair) with 1 views, 0 installs and 73 GitHub stars.