mcp-database-server
Related Servers
Alternatives to mcp-database-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware and secret-safe.15131 npm2MIT
- AlicenseAqualityCmaintenancePrimary purpose is to maintain a self verifying ledger that requires no consesus. Additional features include support for evm compatible and other block chains.615 npm1MIT
- AlicenseNot gradedqualityAmaintenanceLocal-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.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables autonomous financial agents and payment webhooks to create and verify immutable double-entry ledger entries, enforce debit-credit balance invariants, and generate hash-chained audit trails with fraud detection.7MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents an auditable memory layer with provable deletion via signed certificates, a tamper-evident hash-chained audit trail, and bi-temporal time-travel recall over SQLite or Postgres.26 PyPIApache 2.0
- AlicenseCqualityAmaintenanceDeterministic 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.63498 npm32MIT
TDQS
Scored across 4 tools
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.
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.
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.
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.