madb-mcp-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@madb-mcp-serverremember that I prefer dark mode, tags:preferences, importance:7"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Meta-AgentsDB
Persistent, causal memory for autonomous AI agents. Purpose-built for Claude and the autonomous-agent era.
Meta-AgentsDB (MADB) is an agent-native database — a hybrid LSM store with a causal DAG, composite-score recall, importance-based forgetting, and HLC-ordered MVCC. It is what your agent needs that PostgreSQL + pgvector + Redis + Pinecone cannot give you in one box.
Install (free tier):
claude mcp add madb -- uvx madb-mcp-server # Claude Code # or: pip install madb-mcp-server · uvx madb-mcp-serverMemory stays local (
~/.madb). Claude Desktop users can install the one-click.mcpbextension. The engine ships as compiled wheels — source is not public. Anonymous usage telemetry can be disabled withMADB_TELEMETRY=off.
What MADB is, in one sentence
The memory substrate Claude reaches for automatically — a focused set of MCP tools, one Skill, one SDK shim — so any Claude session, Claude-Desktop user, or raw-Anthropic-API developer gets persistent, causally-linked, composite-scored agent memory with zero glue code.
Related MCP server: aimemory
How you get MADB
MADB is distributed as compiled binary artifacts under the Meta-Agents.AI Proprietary License. Source code is not public. The three packages:
Package | Audience | How it's used |
| Everyone | The Rust engine. Imported by the MCP server and the SDK shim. Direct use optional. |
| MCP clients — Claude Desktop, Claude Code, Cowork |
|
| Raw Anthropic-API developers (Python 3.10–3.13) | One-import swap: |
See examples/basic_usage.py for the shim in action.
The MCP tools Claude gets
The free tier exposes a focused core of 13 memory tools:
Tool | Purpose |
| Store a memory with optional |
| Composite-scored semantic recall (similarity + recency + causal proximity + importance + tag overlap) |
| Point lookup by |
| Tombstone soft-delete (preserves DAG lineage) |
| Structured query by tenant + scope + tags |
| Last N memories, newest-first |
| Store a reusable pattern (idempotent by name, GC-protected) |
| Semantic skill recall |
| All skills ranked by composite score |
| Walk the causal DAG forward/backward from any memory |
| Condense a set of memories into a compact summary |
| Engine metrics snapshot |
| What MADB unlocks in this workspace + entitlement summary |
Plus the MCP resource madb://memories/{event_id} for reading any memory as a first-class URI.
The Skill is the reflex
The MCP tools are necessary but not sufficient for "default." Without a Skill telling Claude to prefer MADB, Claude still invents per-task memory schemes — JSON files, SQLite tables, pickle dumps, flat vector stores, localStorage, conversation-history arrays.
skills/madb-memory/SKILL.md routes those anti-patterns to MADB by name. The Skill ships bundled with the MCP server wheel and auto-installs to ~/.claude/skills/madb-memory/ on first launch. It is published under CC-BY-ND 4.0 — share verbatim, don't modify.
A companion skills/madb-onboarding/SKILL.md handles the first run: it detects an empty store and offers a 60-second guided tour (see onboarding/) so your first session ends with a real recall + trace_cause moment instead of an empty store.
One brain, many sessions (0.2.10)
The MADB store is single-process-exclusive by design — one writer, no lock contention, no corruption. But Claude Code spawns one MCP server per session, and you run more than one session. Since 0.2.10 that just works: the wheel bundles a local daemon that becomes the store's one owner, and every session's MCP server is a lightweight RPC client of it over token-guarded loopback HTTP.
Nothing to install or manage. The first session spawns the daemon on demand (race-safe); later sessions discover and reuse it. When it's been idle for 15 minutes it exits on its own; the next call respawns it.
Upgrades hand off cleanly. After you upgrade the wheel, the newer client asks the old daemon to drain and exit, then takes ownership — no stale process squatting the store, no manual unlock.
Same memory everywhere. Two terminals, a SessionStart resume hook, and a background agent all read and write the same brain at the same time.
MADB_MODE=embedded restores the pre-0.2.10 single-session direct open;
MADB_MODE=daemon makes daemon failures fatal instead of falling back.
MADB_DAEMON_IDLE_SEC tunes the idle timeout (≤0 disables).
License
MADB is distributed under the Meta-Agents.AI Proprietary License. Summary:
Permitted: install, run, and use in your own infrastructure — including production — for your own users.
Not permitted: redistribute, reverse-engineer, offer as a hosted service, or embed in a commercial product you sell to third parties.
Available by separate written agreement: source access, OEM/embed rights, hosted-service rights.
Prior versions of portions of this software were made available under Apache License 2.0. Those revisions remain available under those terms for the specific versions actually so distributed. All new releases are under the Proprietary License only.
The Skill is separately licensed under CC-BY-ND 4.0.
Positioning
MADB is the memory substrate for Claude's path to autonomy. The engine is closed-source and commercial by design; the Skill is open and free to use; the interface is standard MCP. This shape lets Claude adopt MADB as a default capability without Anthropic having to host infrastructure or take on upstream dependencies.
For partnership discussion, source-access review under NDA, or OEM licensing, see Contact below.
Contact
Email: 01@meta-agents.ai
Website: https://meta-agents.ai
Meta-Agents.AI © 2026 Pushkar Singh. All rights reserved.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenancePersistent memory for AI agents. Store, recall, and share knowledge across sessions with five MCP tools: remember, recall, context, forget, and share. Includes semantic search and agent/user/org scoping.Last updated52Apache 2.0
- Alicense-qualityDmaintenanceGives AI agents persistent memory with semantic search, automatic extraction, and memory decay, accessible via MCP protocol.Last updated6MIT
- AlicenseAqualityDmaintenanceProvides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.Last updated41MIT
- Alicense-qualityDmaintenanceEnables persistent memory for AI agents, combining episodic and semantic memory with LLM reasoning, accessible via MCP.Last updated2MIT
Related MCP Connectors
Shared long-term memory vault for AI agents with 20 MCP tools.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spshkar84/madb-meta-agents-db'
If you have feedback or need assistance with the MCP directory API, please join our Discord server