Skip to main content
Glama
Sign In
MCP DuckDB Knowledge Graph Memory Server

MCP DuckDB Knowledge Graph Memory Server

by IzumiSy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP DuckDB Knowledge Graph Memory Server

No user-submitted related servers found.

    Related Servers

    • mcp-memory-graphdb

      pavex
      F
      license
      Not graded
      quality
      B
      maintenance
      A persistent graph-database memory server for Claude and other LLM agents, built on the Model Context Protocol and powered by DuckDB.
      3
      -

    • claude-recall

      nhevers
      A
      license
      Not graded
      quality
      D
      maintenance
      A persistent memory server for Claude Code that captures session context and tool outputs to inject relevant history into future sessions. It enables long-term recall through semantic search and automatic context management, allowing for more consistent and context-aware coding interactions.
      10 npm
      253
      ISC

    • MCP Memory Server

      PlumyCat
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude persistent memory by storing conversation context, entities, and enabling semantic search across sessions.
      16 npm
      1
      MIT

    • Knowledge Graph Memory Server

      guinacio
      A
      license
      Not graded
      quality
      D
      maintenance
      A persistent memory system using a local knowledge graph that enables Claude to remember information about users across chats, with advanced search, graph traversal, and filtering capabilities for entities, relations, and observations.
      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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting different aspects of the knowledge graph (entities, relations, observations, nodes), though 'open_nodes' and 'search_nodes' could potentially overlap in functionality if opening involves searching. The descriptions clarify that 'open_nodes' accesses specific named nodes while 'search_nodes' performs query-based lookup, but agents might still confuse them in some scenarios.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming (e.g., add_observations, create_entities, delete_relations). The verbs are clear and appropriate for the actions (add, create, delete, open, search), and there are no deviations in style or convention throughout the set.

    Tool Count5/5

    With 8 tools, this server is well-scoped for a knowledge graph memory system. Each tool appears to serve a specific and necessary function for managing entities, relations, observations, and nodes, without being overly sparse or bloated. The count aligns well with the domain's typical CRUD and query operations.

    Completeness4/5

    The tool set provides strong coverage for core knowledge graph operations, including creation, deletion, and querying of entities, relations, and observations. A minor gap is the lack of update tools (e.g., update_entities or update_relations), which might require workarounds like delete-and-recreate, but the surface is otherwise comprehensive for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources