A side-by-side look at the Memorix and Projectmem 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 Projectmem 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.
No tool names declared yet. Check the project README from the listing page.
Projectmem 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 is categorized under Knowledge & Memory and uses a local stdio subprocess. Projectmem belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Memorix for knowledge & memory work and Projectmem 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. Projectmem 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 riponcm-projectmem 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. Projectmem has 60/100 (Good) with 3 views, 0 installs and 868 GitHub stars.