Recallnest vs Memorix
A side-by-side look at the Recallnest and Memorix 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 Memorix 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.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Memorix when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 59/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 848 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Recallnest | View Memorix |
Tools & capabilities
Recallnest tools
No tool names declared yet. Check the project README from the listing page.
Memorix 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
{
"mcpServers": {
"aliceljy-recallnest": {
"command": "npx",
"args": [
"-y",
"recallnest"
]
}
}
}
Memorix
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix"
]
}
}
}
Frequently asked questions
Recallnest is categorized under Knowledge & Memory and uses a local stdio subprocess. Memorix belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Recallnest for knowledge & memory work and Memorix 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: no auth required. Memorix is listed as free. Auth: no auth required. 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 memorix 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. Memorix has 53/100 (Good) with 2 views, 0 installs and 848 GitHub stars.