DKG Memory MCP Server

MCP (Model Context Protocol) server exposing OriginTrail DKG V10 three-layer verifiable memory (Working / Shared / Verifiable) as standard MCP tools. Mount it in any MCP-capable client — Claude Desktop, Cursor, Claude Code, or a generic MCP agent — and read, write, share and query DKG memory without custom HTTP wiring.

This is a submission to the DKG v10 Call for Integrations (Round 1: Working & Shared Memory). It is a transport-agnostic tooling layer, distinct from the sibling OpenClaw Memory Curator daemon (which is OpenClaw-specific).

Tools

Round 1 scope is Working + Shared Memory only. There is no vm/publish tool (Verifiable Memory is a later round and requires an explicit human-gated publish) and no UI endorsement/voting tool (disallowed by the bounty rules).

Install

npm install -g dkg-memory-mcp

Requires a running DKG V10 node (default http://127.0.0.1:9200) with an auth token at ~/.dkg/auth.token (line 2; comment lines starting with # are stripped).

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "dkg-memory": {
      "command": "dkg-memory-mcp",
      "args": []
    }
  }
}

Cursor / Claude Code

Register the MCP server with command dkg-memory-mcp (stdio transport).

Environment variables (optional)

Development

npm install
node --test test/*.test.js   # unit tests
node src/server.js           # run the stdio server

Smoke test (live)

Verified end-to-end against a DKG V10 node (Base Sepolia testnet): create KA → write quads to Working Memory → SPARQL recall → 3 bindings returned across peer-ID, wallet, and default agent addressing.

License

Apache-2.0