Open Memex vs Dark Memory MCP
A side-by-side look at the Open Memex and Dark Memory MCP 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 Open Memex for databases work; choose Dark Memory MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Dark Memory MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dark_memory_project_create, dark_memory_session_start, dark_memory_session_resume.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Open Memex | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 49/100 · Fair | 59/100 · Good |
| 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 |
Tools & capabilities
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
Dark Memory MCP tools 57
dark_memory_project_createCreate a new project (INV-7 tenant primitive). Idempotent on project_id — re-creating an existing project returns the existing row. The 'default' project is seeded on Open and cannot be re-created (returns ErrAlreadyExists).dark_memory_session_startStart an operational session. Returns the session_id. Use session_close to terminate.dark_memory_session_resumeResume an existing session by session_id. Validates the session exists, sets the active project to match, and returns the session row.dark_memory_session_statusReturn the current state of a session (id, operator, project, status, timestamps). Read-only. Includes closing_soon + seconds_until_close so harnesses can warn before the sweeper closes an idle session.dark_memory_session_closeClose the active session. Returns the write/run/item summary.dark_memory_session_heartbeat
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.
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.
Dark Memory MCP
{
"mcpServers": {
"dark-memory-mcp": {
"command": "npx",
"args": [
"-y",
"@opitacode/dark-memory-mcp"
]
}
}
}
Frequently asked questions
Open Memex is categorized under Databases and uses an install path we have not confirmed yet. Dark Memory MCP belongs to Databases and uses a local stdio subprocess. Pick Open Memex for databases work and Dark Memory MCP 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.
Open Memex is listed as free. Auth: no auth required. Dark Memory MCP 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 open-memex and dark-memory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Open Memex has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 5 GitHub stars. Dark Memory MCP has 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars.