dakera-mcp
OfficialThe dakera-mcp server provides AI agents with a persistent, queryable memory layer featuring smart token management. Here's what you can do:
Store and Manage Memories
Persist facts, decisions, or context with importance weighting (0.0–1.0), tags, memory type (episodic/semantic/procedural/working), optional expiry, and session association (dakera_store).
Recall and Search Memories
Semantic recall (
dakera_recall) — Retrieve top-k memories by vector similarity, with optional time filters and knowledge-graph expansionAdvanced search (
dakera_search) — Semantic search pre-filtered by tags and/or memory typeFull-text search (
dakera_fulltext_search) — BM25 keyword search for exact-term recall (error codes, IDs, names)Hybrid search (
dakera_hybrid_search) — Combined BM25 + vector search in a single pass, tunable viavector_weightBatch recall (
dakera_batch_recall) — Filter-based listing by tags, importance range, time window, type, or session
Delete Memories
dakera_forget— Delete specific memories by ID or bulk-delete by tagdakera_batch_forget— Bulk-delete by filter criteria (tags, importance range, time window, memory type)
Session Management
dakera_session_start— Open a session to group related memories with optional metadatadakera_session_end— Close a session with an optional summary
Knowledge Graph & Extraction
dakera_knowledge_graph— Build a knowledge graph from a seed memory by exploring connections via embedding similaritydakera_extract— Extract structured entities, topics, key phrases, and summaries from free-form text using configurable providers (GLiNER, OpenAI, Anthropic, Ollama, etc.)
Dynamic Tool Discovery & Loading
dakera_discover_tools— Search the tool catalog by keyword or tier without loading full schemasdakera_load_tools— Fetch full input schemas for specific tools on demand to minimize token usage
Key Highlights
Default 14-tool core profile uses ~2,964 tokens; expand to 86 tools via profiles (
admin,power,all) or on-demand loadingScored 88.2% on the LoCoMo benchmark (1,540 questions)
Compatible with Claude, Claude Code, and any MCP-compatible framework
Self-hostable via Docker or Kubernetes
⚡ dakera-mcp
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% on LoCoMo (1,540 questions, standard eval) — benchmark details
Architecture: 14 core tools + on-demand discovery
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:
14 tools loaded by default — the 12 highest-frequency memory operations + 2 meta-discovery tools
On-demand expansion — use
dakera_discover_toolsanddakera_load_toolsto fetch additional tool schemas only when you need them
Default tool set (core profile)
Tool | Purpose |
| Store a memory with importance, tags, and type |
| Semantic recall by query text |
| Advanced memory search with tag/type filters |
| Start a session to group related memories |
| End a session with optional summary |
| Bulk filter-based recall (by tags, importance, time) |
| Delete specific memories by ID |
| Combined vector + BM25 search |
| BM25 full-text search |
| Build a knowledge graph from a seed memory |
| Extract entities and structure from free-form text |
| Bulk delete by tags, type, or time range |
| Search the full tool catalog by keyword or tier |
| Load full schemas for specific tools on demand |
Profiles & token cost
Profile | Tools | ~Tokens | How to enable |
core | 14 | ~2,964 | Default — always loaded |
admin | 32 | ~5,975 |
|
power | 69 | ~13,205 |
|
all | 87 | ~16,212 |
|
Accessing additional tools
# In your agent: discover what's available
dakera_discover_tools(tier="power")
→ returns names + descriptions, no schemas loaded
# Load schemas for the tools you want
dakera_load_tools(tools=["dakera_consolidate", "dakera_agent_stats"])
→ returns full inputSchema for each toolProfile selection
The profile controls which tools appear in tools/list. Three ways to set it:
1. Per-request (in tools/list params):
{"profile": "power"}2. Environment variable (applies to all requests):
DAKERA_MCP_PROFILE=power3. Default: core (14 tools, ~2,964 tokens)
Related MCP server: Zep MCP Server
Run Dakera
The MCP server connects to a Dakera memory server. You need one running first:
docker run -d \
--name dakera \
-p 3300:3300 \
-e DAKERA_ROOT_API_KEY=dk-mykey \
ghcr.io/dakera-ai/dakera:latestFor persistent storage (recommended):
curl -sSfL https://raw.githubusercontent.com/Dakera-AI/dakera-deploy/main/docker-compose.yml \
-o docker-compose.yml
DAKERA_API_KEY=dk-mykey docker compose up -d
curl http://localhost:3300/health # → {"status":"ok"}Full deployment guide (Docker Compose, Kubernetes, Helm): dakera-deploy
Install
npm / npx (Node.js 18+)
# Global install
npm install -g @dakera-ai/dakera-mcp
# Or run directly without installing
npx @dakera-ai/dakera-mcpHomebrew (macOS / Linux)
brew install dakera-ai/tap/dakera-mcpCargo
cargo install dakera-mcpDocker
docker pull ghcr.io/dakera-ai/dakera-mcp:latestBinary download
Pre-built binaries for macOS, Linux, and Windows are available on the releases page.
Platform | File |
macOS (Apple Silicon) |
|
macOS (Intel) |
|
Linux x64 |
|
Linux arm64 |
|
Windows x64 |
|
Connect
Add to .mcp.json (Claude Code) or claude_desktop_config.json (Claude Desktop):
{
"mcpServers": {
"dakera": {
"command": "dakera-mcp",
"env": {
"DAKERA_API_URL": "http://localhost:3300",
"DAKERA_API_KEY": "your-key"
}
}
}
}To start with the power profile (exposes 68 tools):
{
"mcpServers": {
"dakera": {
"command": "dakera-mcp",
"env": {
"DAKERA_API_URL": "http://localhost:3300",
"DAKERA_API_KEY": "your-key",
"DAKERA_MCP_PROFILE": "power"
}
}
}
}Why This Exists
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
Documentation
Related
Repo | What it is |
Python SDK | |
TypeScript SDK | |
CLI | |
Self-host Dakera |
dakera.ai · Documentation · Request Early Access
Part of the Dakera AI open-source ecosystem. Built with Rust. Self-hosted. Zero dependencies.
Maintenance
Latest Blog Posts
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/Dakera-AI/dakera-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server