Dakera

by dakera-ai

Not rated
GitHub

About

Self-hosted Rust-based MCP server for AI agent memory — persistent, queryable memory with hybrid search, knowledge graphs, built-in embeddings, and 14 core tools (expandable to 86+ with profile-based tiering).

Details

Author
dakera-ai
Categories
AI, Knowledge Base, Other

Setup

Install Dakera in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/dakera-ai/dakera-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

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 ofDakera AI— the memory engine for AI agents.

The Dakera memory engine scores88.2% Recall@20 on LoCoMo(1,540 questions · LLM-judge scored) —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 withhybrid tool exposure:

- 14 tools loaded by default— the 12 highest-frequency memory operations + 2 meta-discovery tools
- On-demand expansion— usedakera_discover_toolsanddakera_load_toolsto fetch additional tool schemas only when you need them

# 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 tool

The profile controls which tools appear intools/list. Three ways to set it:

{"profile": "power"}

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:

docker run -d \ --name dakera \ -p 3300:3000 \ -e DAKERA_ROOT_API_KEY=dk-mykey \ ghcr.io/dakera-ai/dakera:latest
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:3000/health # → {"status":"ok"}

Full deployment guide (Docker Compose, Kubernetes, Helm):dakera-deploy

# Global install npm install -g @dakera-ai/dakera-mcp # Or run directly without installing npx @dakera-ai/dakera-mcp
docker pull ghcr.io/dakera-ai/dakera-mcp:latest

Pre-built binaries for macOS, Linux, and Windows are available on thereleases page.

Add to.mcp.json(Claude Code) orclaude_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" } } } }

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.aifor hosted instance
→ Self-host with
dakera-deploy

dakera.ai·Documentation·Request Early Access

Part of the Dakera AI open-core ecosystem. Built with Rust. Self-hosted. Zero dependencies.

Adaptive MCP memory system for AI applications. Learns which retrieval strategies work for your data, scores results using cognitive science models, builds a knowledge graph automatically, and validates every parameter change against real query history before adopting it. Patent pending.

Self-improving MCP memory server for AI agents. One command, no cloud, no config. Hybrid search, feedback loop quality system, dashboard UI, auto-linking knowledge graph. Gets better the more you use it.

Persistent memory for AI agents using a semantic knowledge graph. Store, retrieve, and connect memories with semantic search — so your AI remembers context across sessions.

🏠 🍎 🪟 🐧 - A self-contained Memory server with single-binary architecture (embedded DB & models, no dependencies). Provides persistent semantic and graph-based memory for AI agents.

Smriti is a Model Context Protocol (MCP) server that provides persistent, graph-based memory for LLM applications. Built on LadybugDB (embedded property graph database), it uses EcphoryRAG-inspired multi-stage retrieval - combining cue extraction, graph traversal, vector similarity, and multi-hop association - to deliver human-like memory recall.

MCP-native memory layer for Claude Code, Cursor, Cline, Continue, and 16 other AI tools. Hybrid search (BM25 + pgvector + graph), self-hosted on Supabase + Vercel, 100% MIT, no paywall.

Highly efficient context management for agentic AI: MCP code search, evidence packs, graph context, and memory for large projects.

Self-hosted MCP server giving AI agents persistent memory — Markdown source of truth, hybrid BM25+embedding search, typed graph relations.

Authenticated MCP and agent gateway for Forge Cascade private AI memory, provenance, graph search, and capsule lineage.

mem0-mcp-server — exposes Mem0 persistent semantic memory as an MCP HTTP server; supports add/search/read/update/delete operations and semantic search for agent memory.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.