RushDB MCP Server
OfficialRelated Servers
Alternatives to RushDB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents with persistent semantic memory, including semantic recall, knowledge graphs, and instant domain expertise via pre-built Intelligence Packs.1051 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to store, recall, update, delete, and analyze persistent memories with semantic search, decay, and anomaly retrieval across hosted, self-hosted, or fully local storage modes.46 npm23MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.276 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables persistent, graph-based memory for AI agents, allowing them to store, traverse, and recall relationships between facts, decisions, and context across sessions for efficient reasoning and reduced token usage.MIT

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.1417 npmMIT- AlicenseAqualityCmaintenanceProvides persistent, searchable memory for AI agents, enabling them to retain, recall, and reflect on information across conversations.1932 PyPI1MIT
TDQS
Scored across 48 tools
Many tools overlap heavily: six-plus schema-discovery tools (getSchemaMarkdown, getSchema, getSchemaSummary, findLabels, findProperties, findPropertyById), duplicate deletes (deleteRecord vs deleteRecordById), near-duplicate reads (findRecords/getRecord/getRecordsByIds/findOneRecord/findUniqRecord), overwrite vs partial semantics (setRecord vs updateRecord), and an explicitly deprecated alias (semanticSearch for vectorSearch). The descriptions do try to disambiguate, but an agent must read paragraphs of guidance each time to pick correctly, and redundancy remains.
All names use camelCase and nearly all follow a verb_noun pattern (createRecord, findRelationships, deleteEmbeddingIndex, bulkCreateRecords). A handful (propertyValues, searchValues, resolveNames, smartSearch, helpAddToClient) are noun-first rather than verb-first, which is a minor deviation but still readable and predictable.
48 tools is well past the point where a set stays legible; the schema-discovery and search areas alone account for nearly twenty overlapping entries. Consolidating getSchemaMarkdown/getSchema/getSchemaSummary, deleteRecord/deleteRecordById, and semanticSearch into vectorSearch would cut the surface substantially without losing capability.
Record CRUD, bulk operations, relationship attach/detach/update, schema introspection, pattern inference, embedding and text index lifecycle, vector/keyword/NL search, and CSV export are all present, which is strong coverage for a graph database service. The main gaps are around transactions (tools note they are unavailable inside one) and lack of explicit transaction/session management tools.