Dijin Memory vs Perenna
A side-by-side look at the Dijin Memory and Perenna MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
Dijin MemoryKnowledge & MemoryDijin is a Memory Layer: recall notes, decisions, and evidence-backed answers across every AI.37FairAuth: not declaredVerdict: choose Dijin Memory for knowledge & memory work; choose Perenna 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?
DChoose Dijin Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
Choose Perenna when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VEXOR_CONFIG_JSON, VEXOR_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Dijin Memory | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | VEXOR_CONFIG_JSONVEXOR_API_KEY |
| Verified owner |
Tools & capabilities
Dijin Memory tools
No tool names declared yet. Check the project README from the listing page.
Perenna 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.
Dijin Memory
No confirmed install command for Dijin Memory yet — follow the setup steps linked from its listing page rather than a guessed package name.
Perenna
{
"mcpServers": {
"perenna": {
"command": "uvx",
"args": [
"vexor"
],
"env": {
"VEXOR_CONFIG_JSON": "YOUR_VEXOR_CONFIG_JSON_HERE",
"VEXOR_API_KEY": "YOUR_VEXOR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Dijin Memory is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Perenna belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Dijin Memory for knowledge & memory work and Perenna 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. Dijin Memory has no confirmed install command yet — follow its own setup instructions.
Dijin Memory has no declared pricing — check the project's own site. Perenna 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 dijin-memory and perenna as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dijin Memory has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Perenna has 45/100 (Fair) with 2 views, 0 installs and 61 GitHub stars.
