dark-memory-mcp MCP Server

by opita-code Your server? Claim it

local only

dark-memory-mcp runs on your own machine — the client starts it, so there is no endpoint to ping. 119 installs a week from npm. Last commit 21 Aug 2026.

Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.

Installs per day peak 293 · avg 44 · +60% w/w

a month agotoday

119

Installs / week

npm · @opitacode/dark-memory-mcp

Stars

0 open issues

21 Aug 2026

Last commit

0 releases in 90 days

MIT

License

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1

postinstall: node -e "console.log('dark-memory-mcp installed. Use: dark-memory-mcp or npx @opitacode/dark-memory-mcp')"

File ships in the package but is absent from the source [пакет] index.js:1

этот файл ставится пользователю, но в репозитории его нет

Builds a file path from a variable internal/embedder/onnx/onnx.go:263, internal/server/bootstrap.go:366, internal/orchestration/mcp_research_backend.go:385

    dir := filepath.Join(root, "libonnxruntime", platform)

Runs an external command npm/platform-darwin-arm64/index.js:20, npm/platform-darwin-x64/index.js:20, npm/platform-linux-arm64/index.js:20 и ещё 5

  const child = spawn(BINARY_PATH, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add dark-memory-mcp -- npx -y @opitacode/dark-memory-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "dark-memory-mcp": {
      "args": [
        "-y",
        "@opitacode/dark-memory-mcp"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.dark-memory-mcp]
command = "npx"
args = ["-y", "@opitacode/dark-memory-mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "dark-memory-mcp": {
      "args": [
        "-y",
        "@opitacode/dark-memory-mcp"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "dark-memory-mcp": {
      "args": [
        "-y",
        "@opitacode/dark-memory-mcp"
      ],
      "command": "npx"
    }
  }
}

Alternatives to dark-memory-mcp

same job, measured the same way

Zikkaron

by amanhij

Biologically-inspired persistent memory engine for Claude Code MCP agents

73 installs/wk local only

Agtrepo Memory

by agtrepo

Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.

6 tools answering

Sinter

by shellfu

Persistent, evidence-backed code graph for coding agents.

11 481 installs/wk local only

Limpet

by ksym04

Persistent engineering memory for AI coding agents. Survives refactors, knows when it is stale.

local only

remem-mcp — Local-first MCP Memory + CodeGraph + Wiki

by tinhien11

Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.

92 installs/wk local only

EvolutionDB Long-Term Memory

by alptekin

Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.

9 installs/wk local only

Rigour

by rigour-labs

Quality gates for AI agents. Lint, test, build checks with memory persistence.

1 466 installs/wk local only

Agent Memory MCP

by ipiton

Memory, docs, and repo context layer for engineering agents.

local only

dark-memory-mcp — questions

Answers built from our own checks of this server.

Why is there no uptime for dark-memory-mcp?

dark-memory-mcp runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @opitacode/dark-memory-mcp was installed 119 times last week.

How do I connect dark-memory-mcp?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @opitacode/dark-memory-mcp straight from npm; nothing to host, nothing to sign up for.

How many people use dark-memory-mcp?

The npm package @opitacode/dark-memory-mcp was installed 119 times in the last week. Week over week that is +60%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is dark-memory-mcp open source?

Yes — it is published under the MIT licence, written in Go and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.