Memory Kernel vs Open Memex
A side-by-side look at the Memory Kernel and Open Memex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
Open MemexDatabasesLocal-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.49FairAuth: no auth requiredVerdict: choose Memory Kernel for databases work as a local process; choose Open Memex for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Memory Kernel when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
OChoose Open Memex when
- You need dedicated capabilities in the Databases domain.
- Its auth model fits you: No auth required.
- You want tools like
memory_status, memory_submit, memory_propose.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Open Memex | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Memory Kernel tools
No tool names declared yet. Check the project README from the listing page.
Open Memex tools 6
memory_statusShow the sync queue: outbox drafts, repo review states, uncommitted filesmemory_submitMove named drafts into the repo memory dir (local branch + commit)memory_proposeCopy personal memories into the project scope as review candidatesmemory_promoteAdvance `proposed → approved → published` (or reject / resubmit)memory_resolveList conflicted memory files / 3-way-merge one of themmemory_pr_statusMap the branch PR's GitHub state onto each memory's review state
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.
Memory Kernel
{
"mcpServers": {
"memory-kernel": {
"command": "uvx",
"args": [
"amormorri-memory-kernel"
]
}
}
}
Open Memex
No confirmed install command for Open Memex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Memory Kernel is categorized under Databases and uses a local stdio subprocess. Open Memex belongs to Databases and uses an install path we have not confirmed yet. Pick Memory Kernel for databases work and Open Memex for databases.
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. Open Memex has no confirmed install command yet — follow its own setup instructions.
Memory Kernel has no declared pricing — check the project's own site. Open Memex 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 memory-kernel and open-memex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memory Kernel has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. Open Memex has 49/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.