The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Dakera MCP listing page.
MCP server for Dakera AI. Gives any MCP-compatible AI agent persistent, queryable memory — with smart token management built in.
Works with Claude, Claude Code, and any MCP-compatible framework.
Part of Dakera AI — the memory engine for AI agents.
The Dakera memory engine scores 88.2% Recall@20 on LoCoMo (1,536 evaluated questions · LLM-judged retrieval recall) — benchmark details
Starting every agent session with 60+ tool schemas wastes ~15K tokens before you write a single message. dakera-mcp solves this with hybrid tool exposure:
dakera_discover_tools and dakera_load_tools to fetch additional tool schemas only when you need them| Tool | Purpose |
|---|---|
dakera_store | Store a memory with importance, tags, and type |
dakera_recall | Semantic recall by query text |
dakera_search | Advanced memory search with tag/type filters |
dakera_session_start | Start a session to group related memories |
dakera_session_end | End a session with optional summary |
dakera_batch_recall | Bulk filter-based recall (by tags, importance, time) |
dakera_forget | Delete specific memories by ID |
dakera_hybrid_search | Combined vector + BM25 search |
dakera_fulltext_search | BM25 full-text search |
dakera_knowledge_graph | Build a knowledge graph from a seed memory |
dakera_extract | Extract entities and structure from free-form text |
dakera_batch_forget | Bulk delete by tags, type, or time range |
dakera_discover_tools | Search the full tool catalog by keyword or tier |
dakera_load_tools | Load full schemas for specific tools on demand |
| Profile | Tools | ~Tokens | How to enable |
|---|---|---|---|
| core | 14 | ~2,964 | Default — always loaded |
| admin | 32 | ~5,975 | DAKERA_MCP_PROFILE=admin |
| power | 69 | ~13,205 | DAKERA_MCP_PROFILE=power |
| all | 87 | ~16,212 | DAKERA_MCP_PROFILE=all |
The profile controls which tools appear in tools/list. Three ways to set it:
1. Per-request (in tools/list params):
2. Environment variable (applies to all requests):
3. Default: core (14 tools, ~2,964 tokens)
The MCP server connects to a Dakera memory server. You need one running first:
For persistent storage (recommended):
Full deployment guide (Docker Compose, Kubernetes, Helm): dakera-deploy
Pre-built binaries for macOS, Linux, and Windows are available on the releases page.
| Platform | File |
|---|---|
| macOS (Apple Silicon) | dakera-mcp-aarch64-apple-darwin.tar.gz |
| macOS (Intel) | dakera-mcp-x86_64-apple-darwin.tar.gz |
| Linux x64 | dakera-mcp-x86_64-unknown-linux-musl.tar.gz |
| Linux arm64 | dakera-mcp-aarch64-unknown-linux-musl.tar.gz |
| Windows x64 | dakera-mcp-x86_64-pc-windows-msvc.zip |
Add to .mcp.json (Claude Code) or claude_desktop_config.json (Claude Desktop):
To start with the power profile (exposes 68 tools):
AI agents forget everything when the session ends. Dakera fixes that. This MCP server gives your agent a persistent memory layer with zero infrastructure overhead — point it at a Dakera instance and it works.
The 14-tool default keeps your context window lean. The meta-tools let you expand on demand when you need advanced operations like bulk vector upsert, knowledge graph traversal, or memory federation.
→ dakera.ai for hosted instance
→ Self-host with dakera-deploy
| Repo | What it is |
|---|---|
| dakera-py | Python SDK |
| dakera-js | TypeScript SDK |
| dakera-cli | CLI |
| dakera-deploy | Self-host Dakera |
dakera.ai · Documentation · Request Early Access
Part of the Dakera AI open-core ecosystem. Built with Rust. Self-hosted. Zero dependencies.