Developers
Build agents that remember — and can prove why
Everything you need to wire MADB into your stack: install surfaces, configuration, the tool API, and the privacy model.
Install surfaces
One server, every MCP agent
| Surface | Command |
|---|---|
| Claude Code | claude mcp add madb -- uvx madb-mcp-server |
| pip | pip install madb-mcp-server |
| uvx (zero-install) | uvx madb-mcp-server |
| Anthropic SDK shim | pip install madb-anthropic → from madb_anthropic import Anthropic |
| Desktop | One-click .mcpb Desktop Extension |
Configuration
.mcp.json & environment
{ "mcpServers": { "madb": { "command": "uvx", "args": ["madb-mcp-server"],
"env": { "MADB_DATA_DIR": "~/.madb/data", "MADB_TENANT_ID": "default" } } } }| Variable | Purpose |
|---|---|
MADB_DATA_DIR | Where memory is stored on disk. Defaults to ~/.madb/data. |
MADB_TENANT_ID | Namespace memory per project or workspace (per-tenant memory is available today). |
MADB_TELEMETRY | Set to off to disable the anonymous usage beacon entirely. |
The API
Twelve stable tools
Each accepts an optional tenant_id. Full signatures live in the tool reference.
Privacy
We measure how much, never what
MADB sends an anonymous usage beacon — a salted install id and counts only, never your memory content, queries, or payloads. Disable it anytime with MADB_TELEMETRY=off. Read the full privacy model and security overview.