Skip to main content
Glama
Sign In
dakera-mcp

dakera-mcp

Official
by Dakera-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Related Servers

Alternatives to dakera-mcp

  • MemoryGraph

    memory-graph
    A
    license
    Not graded
    quality
    B
    maintenance
    A graph-based MCP server that provides AI coding agents with persistent memory to store patterns, track complex relationships, and retrieve knowledge across sessions. It leverages graph structures to handle temporal queries and relational paths that traditional vector stores often miss.
    257
    MIT

Related Servers

  • Recall

    Recallofficial

    RecallWorks
    A
    license
    Not graded
    quality
    D
    maintenance
    Open-source MCP memory server for AI agents — persistent, searchable, tiered memory across sessions. Works over stdio (Cursor, Claude Desktop) or HTTP+SSE. MIT licensed.
    21 PyPI
    8
    MIT

  • project-memory-mcp

    kaaustubh
    A
    license
    A
    quality
    C
    maintenance
    Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
    16
    91 npm
    1
    MIT

  • Inkwell

    veronchenko
    A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted MCP server giving AI agents persistent memory — Markdown source of truth, hybrid BM25+embedding search, typed graph relations.
    3
    MIT

  • MemVault

    dreamor
    A
    license
    A
    quality
    B
    maintenance
    A self-hosted MCP memory server that gives every MCP-compatible agent a shared, persistent memory layer, so preferences, project conventions, and past decisions carry across sessions and across different agents and vendors. It combines hybrid keyword-plus-vector retrieval with automatic context injection, zero-config sync, and selective injection of memories by agent and priority.
    20
    2
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation3/5

The memory-retrieval surface is crowded: dakera_recall, dakera_search, dakera_fulltext_search, dakera_hybrid_search and dakera_batch_recall all return memories, and recall vs search in particular differ only in framing (session neighbours, pre-filters) that an agent must read carefully to distinguish. Store/forget, forget/batch_forget, session_start/session_end, and discover_tools/load_tools are otherwise clearly separated, and the descriptions do actively steer selection.

Naming Consistency4/5

All names share the dakera_ prefix and snake_case, with verb-first forms dominating (store, forget, recall, search, extract, load_tools). Minor deviations are the noun-only dakera_knowledge_graph and the noun-first session_start/session_end forms, but the set remains highly predictable.

Tool Count4/5

14 tools is a reasonable scope for a memory/KG server, covering write, delete, retrieval, sessions, graph exploration, extraction and catalog meta-tools. Slightly heavy on the retrieval side, where five near-parallel search tools inflate the count, but nothing feels gratuitous.

Completeness2/5

Multiple descriptions point agents at tools that are not in this set — dakera_memory_importance (suggested repeatedly as the non-destructive alternative to forgetting), dakera_graph_traverse and dakera_auto_tag — creating guaranteed dead ends. There is also no update/edit or importance-adjust operation, so stored memories can only be created or destroyed, not amended.

Maintenance

ActivityMaintained
ResponsivenessMixed handling

Resources