Skip to main content
Glama
fireproof-storage

mcp-database-server

by fireproof-storage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-database-server

No user-submitted related servers found.

    Related Servers

    • W3 Ledger MCP Server

      baskcart
      A
      license
      A
      quality
      C
      maintenance
      Primary purpose is to maintain a self verifying ledger that requires no consesus. Additional features include support for evm compatible and other block chains.
      6
      13
      1
      MIT

    • USRCP

      frank-bot07
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server providing a shared, AES-256-GCM encrypted SQLite ledger of structured user state (stack, projects, preferences) that any MCP-aware tool can read/write, with user-held keys and optional zero-knowledge sync.
      1
      Apache 2.0

    • Neotoma

      markmhendrickson
      A
      license
      C
      quality
      A
      maintenance
      Deterministic state layer for AI agents that stores versioned entities such as contacts, tasks, transactions, and decisions with immutable observations and full provenance. Local-first SQLite memory shared across Claude, Cursor, ChatGPT, Codex, and OpenClaw via MCP and native plugins.
      63
      176
      32
      MIT

    • agent-memory-os

      yamantaka520
      A
      license
      A
      quality
      A
      maintenance
      Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.
      12
      5
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: load retrieves, save creates/updates, delete removes, and query searches documents. The descriptions make it easy for an agent to select the right tool for each operation without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., load_json_doc, save_json_doc) with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance.

    Tool Count5/5

    With 4 tools, this server is well-scoped for basic JSON document operations. Each tool earns its place by covering essential CRUD-like functions (load, save, delete, query), which is appropriate for a database server focused on JSON documents.

    Completeness5/5

    The tool set provides complete coverage for the domain of JSON document management: it includes create/update (save), read (load), delete, and query operations. There are no obvious gaps, and agents can perform full lifecycle tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources