ZizkaDB

io.github.ZIZKA-AI-SLPublished by GitHub account ZIZKA-AI-SLv0.1.13Updated Nov 7, 2026

Causal memory and tamper-evident audit log for AI agents: log, why, search, time travel.

VerifiedSTDIODesktop onlyDatabasesKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

ZizkaDB MCP server gives an AI agent persistent memory, keyword and semantic search, causal debugging, time travel and a verifiable audit log.

What you can do
  • Log events and the reasons behind them into a persistent agent memory
  • Search stored history by keyword and by semantic similarity
  • Trace causal chains for debugging and replay past states with time travel
  • Verify that the recorded history has not been altered (verify_chain)
  • Show logged events on the ZizkaDB dashboard within seconds
When to use it
Useful when an agent needs memory that survives across sessions, or when you want an auditable, tamper-evident record of what an agent did and why. Also suited to debugging agent behavior by tracing causes and revisiting earlier states.
Requirements
Runs locally over stdio, installed from PyPI (pip install zizkadb-mcp or uvx, which needs uv). For the managed cloud you need a ZizkaDB account, an agent created in the dashboard, and its key in ZIZKADB_API_KEY; the agent name in log calls must match the key. Self-hosting sets ZIZKADB_HOST (for example a localhost URL), where a dev key is auto-injected.
Before you install
The API key (ZIZKADB_API_KEY) is a live credential copied once at creation; keep it out of shared configs. Logged events are sent to the configured ZizkaDB host, which is the cloud service by default, so agent history leaves the machine. An anonymous install ping is sent at startup unless ZIZKADB_TELEMETRY is set to false. Signing up alone does not log events; a key must be configured.

Installation

In SourceWeft

  1. Open ZizkaDB in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

zizkadb-mcp

PyPI: zizkadb-mcp 0.1.13 · listed in the MCP Registry as io.github.ZIZKA-AI-SL/zizkadb-mcp

MCP server for ZizkaDB. Gives any MCP-compatible AI agent persistent memory, keyword and semantic search, causal debugging, time travel, and proof that its history is untouched (verify_chain).

Setup (managed cloud)

  1. Sign up at db.zizka.ai
  2. Dashboard → Create agent (e.g. cursor-agent) — copy the API key shown once
  3. Paste the key into your MCP config (see below)
  4. Reload MCP in Cursor — use the same agent name in log_event calls
  5. Events appear on your dashboard within seconds

Agent name must match. If your key is for cursor-agent, log with agent="cursor-agent". For many dynamic agent names, use a tenant-wide key (Settings).

Signup alone does not log events. You must create an agent + key and add it to ZIZKADB_API_KEY.

Cursor — 30 second setup

Paste into ~/.cursor/mcp.json (or .cursor/mcp.json in your project), then reload MCP:

json
{  "mcpServers": {    "zizkadb": {      "command": "uvx",      "args": ["zizkadb-mcp"],      "env": { "ZIZKADB_API_KEY": "zizkadb_live_xxxx" }    }  }}

Self-host: use the Self-hosted block below (ZIZKADB_HOST only — dev key auto-injected on localhost).

Prerequisite: install uv for uvx:

bash
curl -LsSf https://astral.sh/uv/install.sh | sh

Install

bash
pip install zizkadb-mcp# oruvx zizkadb-mcp

Self-hosted

json
{  "mcpServers": {    "zizkadb": {      "command": "uvx",      "args": ["zizkadb-mcp"],      "env": {        "ZIZKADB_HOST": "http://localhost:8000"      }    }  }}

On localhost, the dev key (zizkadb_dev_local) is auto-injected — no API key needed. Must match DEV_API_KEY in infra/.env if you changed it.

Environment variables

VariableDefaultPurpose
ZIZKADB_HOSThttps://db.zizka.aiAPI base URL
ZIZKADB_API_KEY—Required on cloud. Your key from db.zizka.ai Settings
AGENTDB_API_KEY—Legacy alias for ZIZKADB_API_KEY
AGENTDB_HOST—Legacy alias for ZIZKADB_HOST
ZIZKADB_TELEMETRYonSet false to opt out (anonymous install ping when MCP server starts)

If ZIZKADB_API_KEY is missing on cloud, MCP tools return a clear error instead of silently failing.

Links

Source: mcp/README.md at commit 233ae38

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.13LatestNov 7, 2026
  2. v0.1.12Oct 31, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts