Memorix vs Linksee Memory
A side-by-side look at the Memorix and Linksee Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Memorix for knowledge & memory work as a local process; choose Linksee 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 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.
Choose Linksee Memory 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 | 53/100 · Good | 57/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 | 848 | 15 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Memorix | View Linksee Memory |
Tools & capabilities
Memorix tools
No tool names declared yet. Check the project README from the listing page.
Linksee 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.
Memorix
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix"
]
}
}
}
Linksee Memory
{
"mcpServers": {
"michielinksee-linksee-memory": {
"command": "npx",
"args": [
"-y",
"linksee-memory"
]
}
}
}
Frequently asked questions
Memorix is categorized under Knowledge & Memory and uses a local stdio subprocess. Linksee Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Memorix for knowledge & memory work and Linksee 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.
Memorix is listed as free. Auth: no auth required. Linksee Memory 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 memorix and michielinksee-linksee-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memorix has a quality signal of 53/100 (Good) with 2 views, 0 installs and 848 GitHub stars. Linksee Memory has 57/100 (Good) with 4 views, 0 installs and 15 GitHub stars.