Cortex vs Basic Memory — MCP Server Comparison | AllMCPs
Cortex vs Basic Memory
A side-by-side look at the Cortex and Basic Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cortex for knowledge & memory work over a hosted endpoint; choose Basic 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 Cortex when
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer a remote HTTP/SSE transport.
You have the keys it needs: CORTEX_ACCESS_TOKEN, CORTEX_MCP_URL.
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.
Cortex is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Basic Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Cortex for knowledge & memory work and Basic 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.
Cortex has no declared pricing — check the project's own site. Basic Memory is listed as freemium — a free tier with paid plans. 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 cortex-5 and basicmachines-co-basic-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cortex has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Basic Memory has 64/100 (Good) with 2 views, 0 installs and 4,141 GitHub stars.