Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
Dakera-AI avatar

Dakera Mcp

  • 8 repo stars
  • Updated July 27, 2026
  • Dakera-AI/dakera-mcp

Dakera MCP is a MCP server that provides decay-weighted vector memory and 83 tools for store, recall, search, and knowledge graphs for AI agents.

About

Dakera MCP is a Model Context Protocol server that gives AI coding agents decay-weighted vector memory and a large tool surface for persistence. developers shipping agent features, copilots, or internal tools can register the server in Claude Code, Cursor, or other MCP clients so the model can store facts, recall them later, run searches, and work with knowledge graphs instead of re-explaining context every session. The catalog positions it in the Build phase under agent tooling because memory backends are usually integrated while you are designing agent architecture, though the same memory pays off when you operate and iterate on production behavior. Install via the published OCI package with stdio transport. It is an MCP integration layer, not a standalone chat skill—your agent orchestrates when to call each of the 83 tools.

  • 83 MCP tools for store, recall, semantic search, and knowledge-graph operations
  • Decay-weighted vector memory so older facts fade unless reinforced
  • stdio transport via OCI image ghcr.io/dakera-ai/dakera-mcp
  • Local-first style memory suitable for long-running agent workflows
  • Version 0.9.8 in the official MCP server schema

Dakera Mcp by the numbers

  • Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add DakeraMcp -- npx -y Dakera-AI/dakera-mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars8
Last updatedJuly 27, 2026
RepositoryDakera-AI/dakera-mcp

What it does

Give Claude Code or Cursor a persistent, decay-weighted memory layer so agents remember context across sessions without stuffing the context window.

Who is it for?

Best when you're adding durable memory to Claude Code or Cursor workflows, RAG-style agents, or multi-step coding pipelines that need recall without a custom vector DB integration.

Skip if: Skip if you only need a simple notes search in Obsidian or read-only analytics on an existing SaaS backend with no agent memory requirements.

What you get

After you register Dakera MCP, your agent can persist and retrieve weighted memories and graph-linked knowledge through standard MCP tool calls across sessions.

  • MCP-configured agent with memory store/recall/search tools
  • Decay-weighted retention behavior for agent-held facts
  • Knowledge-graph-oriented tool calls usable from the agent loop

By the numbers

  • 83 MCP tools documented in the server description
  • Server version 0.9.8
  • stdio transport via OCI identifier ghcr.io/dakera-ai/dakera-mcp:0.9.8
README.md

⚡ dakera-mcp

CI Crate npm Downloads License: MIT LoCoMo 88.2% Glama Docs dakera.ai Playground

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_tools and dakera_load_tools to fetch additional tool schemas only when you need them

Default tool set (core profile)

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

Profiles & token cost

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

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 tool

Profile 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=power

3. Default: core (14 tools, ~2,964 tokens)


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:latest

For 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-mcp

Homebrew (macOS / Linux)

brew install dakera-ai/tap/dakera-mcp

Cargo

cargo install dakera-mcp

Docker

docker pull ghcr.io/dakera-ai/dakera-mcp:latest

Binary download

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

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

Full docs
MCP reference

Related

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-source ecosystem. Built with Rust. Self-hosted. Zero dependencies.

Recommended MCP Servers

How it compares

Long-horizon agent memory MCP server, not a single-purpose research or analytics connector.

FAQ

Who is Dakera MCP for?

Developers building AI agents or heavy MCP-driven coding workflows who want vector memory and knowledge graphs without wiring a separate memory stack by hand.

When should I use Dakera MCP?

Use it during Build when you are integrating agent persistence, or when Operate/iterate cycles need the agent to remember prior decisions, bugs, and customer context with decay-weighted recall.

How do I add Dakera MCP to my agent?

Add the stdio MCP entry pointing at the OCI image ghcr.io/dakera-ai/dakera-mcp:0.9.8 in your Claude Code, Cursor, or Windsurf MCP config per your client’s server.json format.

AI & LLM Toolsagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.