InvariantDB ships a Model Context Protocol server. One config line gives your agent durable memory it can trust, prove, and replay: bitemporal Cypher (what was true, when), provenance walks (why the agent thought that), 14 tools total. JSON-RPC 2.0 over HTTPS; auth via Authorization: Bearer gq_....
Pair with an API key from /apikeys. HTTP transport is the recommended path — see the self-hosted section below for on-prem deployments.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"invariantdb": {
"type": "http",
"url": "https://invariantdb.com/e/mcp",
"headers": {
"Authorization": "Bearer gq_paste_your_api_key_here"
}
}
}
}
Restart Claude Desktop. The 14 tools appear under the plug icon.
The same shape works in any MCP-compatible client. The endpoint is https://invariantdb.com/e/mcp; auth is Authorization: Bearer gq_…. Use your client's HTTP MCP transport config.
Read the graph, search it, remember an agent session, and answer a compliance question — all through the same MCP endpoint, all landing in the same tamper-evident audit chain.
Arbitrary Cypher against the bound graph. Returns columns + rows in the engine's standard wire shape. Parameters substitute for $name placeholders.
Look up one node by its string id. Cheap, no scan.
Look up one edge by its string id.
Returns graph_dir + current_snapshot_seq + auth summary. Useful first call to confirm the connection is healthy.
BM25 fulltext via tantivy over (label, property). Returns top-k hits with score.
HNSW vector search via instant-distance. Returns top-k hits with score. Metric: cosine | euclidean | dot.
Record one event in an agent's session — per-agent sequential log. kind is operator-defined: observation, thought, toolCall, decision, etc. Yields the event id and timestamp.
Replay an agent's session — last N events, time-ordered. Use it to show a user what the agent did, or feed past context back into the next prompt.
Walk every version of a belief + its evidence. The full inference-revision history: what the agent believed, when, and why.
Full bitemporal version history + provenance (actor, source, reason, confidence) for one node property. ECOA adverse-action explanations, AI decision audits.
Walk derived-from edges back from a node — RAG citation chains, inference trees, document derivation. depth limits the walk.
Replay the hash-chained ACL audit log. Who tried to read what, when, and whether the engine denied them. Pair with db.verifyAclChain for tamper-evidence.
GDPR Article 20 right-to-portability. One call returns every atom of the subject's data: node, every incident edge, full bitemporal version history, plus provenance for each property.
GDPR Article 17 crypto-shred. Destroys the subject's encryption key (irreversible). Every encrypted property for that subject becomes unrecoverable ciphertext — retroactively across every snapshot, backup, and audit replay. Returns a signed receipt your DPO hands the subject.
CREATE / SET / DELETE unless you flip the explicit allow-mutate flag.db.verifyAclChain at any time.If you run your own InvariantDB cluster, the MCP endpoint is at POST /mcp (default graph) or POST /graphs/{name}/mcp (named graph) on your InvariantDB endpoint. Auth is the same API-key gate.
See the SDK page for client invocation examples.
By design, the MCP surface is a read-and-replay surface. Operations that change schema, manage tenancy, or control infrastructure — creating graphs, dropping data, issuing API keys, maintenance operations — stay on the HTTP surface where they belong: behind admin-role gates and not adjacent to whatever the agent decided to do this turn.
If you want to give an agent broader access, mint a separate API key with explicit role and scope and pass it through — don't widen the MCP server's default surface.
Bitemporal recall, provenance walks, and a tamper-evident audit chain — through one MCP endpoint and one bearer token.