Memora vs Cortex
A side-by-side look at the Memora and Cortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Memora for knowledge & memory work as a local process; choose Cortex for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Memora 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 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 56/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed |
Tools & capabilities
Memora tools
No tool names declared yet. Check the project README from the listing page.
Cortex 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.
Memora
{
"mcpServers": {
"agentic-mcp-tools-memora": {
"command": "uvx",
"args": [
"memora-mcp"
]
}
}
}
Cortex
{
"mcpServers": {
"cortex-5": {
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
}
Frequently asked questions
Memora is categorized under Knowledge & Memory and uses a local stdio subprocess. Cortex belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Memora for knowledge & memory work and Cortex 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.
Memora is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: no auth required. Cortex 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 agentic-mcp-tools-memora and cortex-5 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memora has a quality signal of 56/100 (Good) with 3 views, 0 installs and 735 GitHub stars. Cortex has 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.