In-depth architectural comparison of the Dark Memory MCP and Memory Kernel MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Dark Memory MCP
Databases · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Memory Kernel
Databases · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Dark Memory MCP if you need specialized Databases tools running via a local process. Choose Memory Kernel if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Dark Memory MCP when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Create 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_start
Start an operational session. Returns the session_id. Use session_close to terminate.
dark_memory_session_resume
Resume an existing session by session_id. Validates the session exists, sets the active project to match, and returns the session row.
dark_memory_session_status
Return 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_close
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Dark Memory MCP is categorized under Databases and uses a local stdio subprocess. In contrast, Memory Kernel belongs to Databases using local stdio subprocess. Select Dark Memory MCP when you need capabilities focused on databases and Memory Kernel when you require tools for databases.
Close the active session. Returns the write/run/item summary.
dark_memory_session_heartbeat
Refresh 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_recover
Detect 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_resurrect
Resurrect 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_topic
Run a research query against the registered ResearchBackend set. Returns deduplicated, confidence-ranked items.
dark_memory_research_recall
Recall previously stored research items by query, with a token budget. Runs the Atlan 5-bucket economy pipeline.
dark_memory_research_resume_thread
Continue a multi-turn research thread by re-running ResearchTopic with the same thread_id.
dark_memory_agent_bootstrap
Return 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.