Iai Personal Memory Engine vs Cognitive AI Memory
A side-by-side look at the Iai Personal Memory Engine and Cognitive AI Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Iai Personal Memory Engine for knowledge & memory work; choose Cognitive AI 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 Iai Personal Memory Engine when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
- You want tools like
memory_recall, memory_temporal_recall, memory_recall_structural.
Choose Cognitive AI Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 60/100 · Good | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 912 | 270 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Iai Personal Memory Engine | View Cognitive AI Memory |
Tools & capabilities
Iai Personal Memory Engine tools 9
memory_recallCue-based recall — returns hits **and anti-hits**: memories that *contradict* the cue surface next to the ones that match, so a stale fact can't masquerade as current.memory_temporal_recallTime-anchored recall — *"what did I say about pricing in May?"*memory_recall_structuralRetrieve by the *shape* of a memory (the HD substrate), not just its embedding.memory_searchPlain text search over the store.memory_captureWrite a memory explicitly (ambient capture normally does this for you).memory_contradictRecord that a fact changed. The old version is archived, not erased — both stay retrievable. That's the Rescue@10 and historical-verbatim story in the [benchmarks](#benchmarks).memory_reinforceStrengthen a memory's recall pathways.memory_consolidateRun a consolidation pass now instead of waiting for idle.profile_get_setThe eleven sealed procedural knobs the engine learns about you.
Cognitive AI Memory 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.
Iai Personal Memory Engine
No confirmed install command for Iai Personal Memory Engine yet — follow the setup steps linked from its listing page rather than a guessed package name.
Cognitive AI Memory
{
"mcpServers": {
"cognitive-ai-memory": {
"command": "uvx",
"args": [
"yourmemory"
]
}
}
}
Frequently asked questions
Iai Personal Memory Engine is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Cognitive AI Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Iai Personal Memory Engine for knowledge & memory work and Cognitive AI 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. Iai Personal Memory Engine has no confirmed install command yet — follow its own setup instructions.
Iai Personal Memory Engine is listed as free. Auth: no auth required. Cognitive AI Memory 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 codeabra-iai-personal-memory-engine and cognitive-ai-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Iai Personal Memory Engine has a quality signal of 60/100 (Good) with 3 views, 0 installs and 912 GitHub stars. Cognitive AI Memory has 44/100 (Fair) with 3 views, 0 installs and 270 GitHub stars.