Dark Memory MCP vs Memory Find
A side-by-side look at the Dark Memory MCP and Memory Find MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
Memory FindDatabasesLocal, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.36FairAuth: no auth requiredVerdict: choose Dark Memory MCP for databases work as a local process; choose Memory Find for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
MChoose Memory Find when
- You need dedicated capabilities in the Databases domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MEMORS_HOME, MEMORS_KB.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Memory Find | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 59/100 · Good | 36/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 | MEMORS_HOMEMEMORS_KB |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 57 | Not listed |
| Full listing | View Dark Memory MCP | View Memory Find |
Tools & capabilities
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_heartbeatRefresh a session's last_heartbeat_at so the sweeper does not auto-close it. Call every ~30s during long reasoning pauses or read-only stretches (>60m between writes would otherwise demote the session to closed_aborted). Returns the new last_heartbeat_at.dark_memory_session_recoverDetect the most-recent closed_aborted session for an operator within a lookback window (INV-8). Read-only: never creates a session. Returns the candidate + requires_consent=true when found, so the caller can decide to follow up with session_resurrect.dark_memory_session_resurrectResurrect a closed_aborted session (INV-8): creates a new session inheriting the original's constitution binding + active mods. The original stays untouched. Use session_recover first to discover the candidate. Returns the new session_id + inheritance audit.dark_memory_research_topicRun a research query against the registered ResearchBackend set. Returns deduplicated, confidence-ranked items.dark_memory_research_recallRecall previously stored research items by query, with a token budget. Runs the Atlan 5-bucket economy pipeline.dark_memory_research_resume_threadContinue a multi-turn research thread by re-running ResearchTopic with the same thread_id.dark_memory_agent_bootstrapReturn the markdown content of a dark-agent self-bootstrap resource by surface+target. Surfaces: system_prompt | compatibility_matrix | install_guide (requires target) | companion (requires target) | all. The resource URIs are also exposed via resources/read for harnesses that prefer the standard MCP path.- +45 more on the listing page
Memory Find 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.
Dark Memory MCP
{
"mcpServers": {
"dark-memory-mcp": {
"command": "npx",
"args": [
"-y",
"@opitacode/dark-memory-mcp"
]
}
}
}
Memory Find
No confirmed install command for Memory Find yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Dark Memory MCP is categorized under Databases and uses a local stdio subprocess. Memory Find belongs to Databases and uses an install path we have not confirmed yet. Pick Dark Memory MCP for databases work and Memory Find 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. Memory Find has no confirmed install command yet — follow its own setup instructions.
Dark Memory MCP has no declared pricing — check the project's own site. Memory Find 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 dark-memory-mcp and memory-find as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dark Memory MCP has a quality signal of 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Memory Find has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.