Usecortex MCP vs Memorix
A side-by-side look at the Usecortex MCP 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 Usecortex MCP for knowledge & memory work over a hosted endpoint; 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 Usecortex MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
query_knowledge, list_topics, add_knowledge.
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 | 51/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 848 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Usecortex MCP | View Memorix |
Tools & capabilities
Usecortex MCP tools 5
query_knowledgeAsk a natural language question and get an AI-powered answer based on your stored knowledge.list_topicsList all knowledge topics. Takes no parameters.add_knowledgeWrite new knowledge to your base. Your agent can store discoveries, decisions, or patterns it finds.get_topicRetrieve all knowledge entries for a specific topic.search_knowledgeSearch knowledge entries by keyword (text match).
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.
Usecortex MCP
{
"mcpServers": {
"darktw-usecortex-mcp": {
"url": "https://api.usecortex.net/mcp"
}
}
}
Memorix
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix"
]
}
}
}
Frequently asked questions
Usecortex MCP is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Memorix belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Usecortex MCP 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.
Usecortex MCP is listed as freemium — a free tier with paid plans. Auth: api key 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 darktw-usecortex-mcp and memorix as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Usecortex MCP has a quality signal of 51/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Memorix has 53/100 (Good) with 2 views, 0 installs and 848 GitHub stars.