dkg-memory-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
DKG Memory MCP Server
MCP (Model Context Protocol) server exposing OriginTrail DKG V10 memory (Working and Shared Memory in Round 1; no VM tools) 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
Tool | Purpose |
| Node + context-graph health |
| Write quads to a named Knowledge Asset in Working Memory |
| SPARQL query over a memory view (working / shared / verifiable) |
| List Knowledge Assets + lifecycle state |
| Promote a KA to Shared Working Memory (seals by default) |
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).
Related MCP server: mycelial-brain-mcp
Install
npm install -g dkg-memory-mcpRequires 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)
Variable | Default |
|
|
|
|
| auto (node default agent) |
Development
npm install
node --test test/*.test.js # unit tests
node src/server.js # run the stdio serverSmoke 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
Verified example (2026-08-22)
Real MCP round-trip against the local DKG node (v10.0.19, testnet), driven over the stdio MCP protocol:
// tools/call dkg_write_memory
{
"kaName": "hermes-audit-manic",
"subject": "urn:dkg:hermes:demo:manic-deposit",
"triples": [
{"predicate": "http://127.0.0.1:7878/actionType", "object": "deposit"},
{"predicate": "http://127.0.0.1:7878/chain", "object": "solana"},
{"predicate": "http://127.0.0.1:7878/outcome", "object": "success"}
]
}
// -> Created Knowledge Asset "hermes-audit-manic-1787398447058" with 4 quad(s)
// assertionUri: did:dkg:.../_working_memory/.../269
// status: wm-sealed | merkleRoot: 0x8aa210f8... | written: 4
// tools/call dkg_query_memory (SPARQL)
{"query": "SELECT ?s ?p ?o WHERE { ?s <http://127.0.0.1:7878/actionType> \"deposit\" . ?s ?p ?o }", "view": "working"}
// -> returns the deposited action quads (incl. records written by sibling tools)The write sealed to Working Memory (EIP-712 seal, merkle-rooted) and the SPARQL
query recalled it back, including records written by the sibling
dkg-hermes-bridge — demonstrating cross-tool visibility on the shared DKG
substrate.
Recorded walkthrough
docs/demo.gif is a recorded walkthrough of this integration against a live local
DKG V10 node (raw recording: docs/demo.cast, asciinema v2 format).
docs/demo-transcript.txt is the exact terminal output of that same run.

Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MEOK ABCI Bridge MCP — read-only Tendermint / Cosmos blockchain query for agents. Built-in registry
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceConnects MCP-compatible agents with the OriginTrail Decentralized Knowledge Graph, enabling creation, retrieval, linking, and exchange of verifiable knowledge using natural language and SPARQL queries.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, write, search, and manage persistent, decentralized context memory via a GCS-backed MCP server, with tools for document storage, retrieval, and STIM protocol nuggets.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to interact with an EverOS v2 memory store over local Streamable HTTP, providing read-only memory tools and an opt-in, approval-gated write capability.-

MemoryOS MCP Serverofficial
AlicenseCqualityBmaintenanceEnables agent runtimes, IDEs, and local AI tools to access and manage MemoryOS tenant memory, domain schemas, and cross-agent universal memory through Model Context Protocol tools.26MIT