Skip to main content
Glama
rush-db

RushDB

by rush-db
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to RushDB

No user-submitted related servers found.

    Related Servers

    • smriti

      Smriti-AA
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightning-fast, self-hosted knowledge store and memory layer for AI agents
      -
    • RushDB MCP Server by rush-db

      RushDB MCP Serverofficial

      rush-db
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to gain persistent, structured memory that is semantically searchable and graph-traversable, allowing them to store and query records and relationships without managing embeddings or schemas.
      43
      40 npm
      Apache 2.0

    • dejaview-mcp

      JakeC77
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.
      MIT

    • Personal Neo4j Memory Server

      jeelidev
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with persistent, graph-based memory using Neo4j, enabling semantic search and complex relationship tracking. It features specialized Cloudflare Access support for secure remote connections and isolated multi-database management for different projects.
      10 npm
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear boundaries, such as CreateRecord vs. UpdateRecord vs. DeleteRecord. However, there is some overlap between DeleteRecord and DeleteRecordById (described as aliases), and FindOneRecord vs. FindUniqRecord could be confusing without careful reading of descriptions, though the latter emphasizes uniqueness.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., CreateRecord, DeleteRecord, FindRecords) with clear action-object pairs. Minor deviations include GetQueryBuilderPrompt and HelpAddToClient, which are more descriptive but still maintain readability without disrupting the overall pattern.

    Tool Count3/5

    With 29 tools, the count feels heavy for a database server, potentially overwhelming for agents. While it covers many operations, it could be streamlined by merging redundant tools like DeleteRecord and DeleteRecordById, or consolidating some find operations to reduce complexity.

    Completeness5/5

    The tool set provides comprehensive coverage for database operations, including CRUD (CreateRecord, GetRecord, UpdateRecord, DeleteRecord), bulk operations, relationships (AttachRelation, DetachRelation), transactions, and utilities like export and settings. No obvious gaps exist for core database workflows.

    Resources