Skip to main content
Glama
ArcadeDB Multi-Model DBMS

ArcadeDB Multi-Model DBMS

Official
by ArcadeData

Related Servers

Alternatives to ArcadeDB Multi-Model DBMS

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Shared memory and a knowledge graph for AI agents: hybrid vector and keyword search, RAG over your docs, scoped agent memory, and RDF/SPARQL and Cypher graph queries. Works without an embedding model; one server can serve many agents.
      477
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightning-fast, self-hosted knowledge store and memory layer for AI agents
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables persistent agent memory and document ingestion with hybrid vector and lexical retrieval, memory lifecycle management, graph-backed entities, preferences, facts, and cited search through ArcadeDB. It also supports provider-agnostic embeddings and reranking, durable file processing, and optional governance/redaction hooks.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server for readonly-first access to Oracle, SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, and Qdrant vector search.
      78 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Munin is a high-performance, pragmatic memory layer for AI agents (Cursor, Claude Code, OpenClaw, Gemini CLI,...). Unlike other solutions, Munin focuses on developer productivity with: * Multi-Project Support: Isolate memories into separate "brains" (Context Cores). * GraphRAG: Automatically builds a knowledge graph from your context. * Sub-200ms Search: Blazing fast Hybrid & Semantic
      3
      -

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clearly distinct concern: server admin (status, settings), profiler lifecycle (start/stop/status), and database operations (list, schema, query, execute). No two tools overlap in purpose, making misselection unlikely.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern: profiler_start/stop/status, get_server_settings, set_server_setting, list_databases, get_schema, execute_command, query, server_status. The only slight deviation is 'execute_command' and 'query' which use more generic verbs rather than a resource-specific noun, and 'server_status' uses a different word order than get_/set_ prefixes.

    Tool Count5/5

    Ten tools is well-scoped for a DBMS server MCP. Each tool maps to a meaningful operation a client would need: server introspection, config management, profiling, and database CRUD/querying. Nothing feels redundant or missing at the top level.

    Completeness4/5

    The surface covers server status, configuration management, profiling, database enumeration, schema retrieval, and both read and write operations. Minor gaps include no database creation/deletion and no explicit way to retrieve saved profiler results from disk, but the core admin+query workflow is complete.

    Maintenance

    ActivityActive
    ResponsivenessSyncing