zizkadb-mcp

MCP server for ZizkaDB. Gives any MCP-compatible AI agent persistent memory, semantic search, causal debugging, and time travel.

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:

{
  "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:

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

Install

pip install zizkadb-mcp
# or
uvx zizkadb-mcp

Self-hosted

{
  "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

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

Links

• Docs
• GitHub