@jaydb/mcp
Related Servers
Alternatives to @jaydb/mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, read, update, and delete data in local-first apps built with the Jazz framework, with support for sync, auth, and rich data types.1-
- FlicenseBqualityDmaintenanceEnables AI assistants to directly manage database tables, execute SQL, and handle user operations in iadev projects from the editor.15-
- AlicenseAqualityDmaintenanceEnables AI assistants to read, write, query, and manage JSON data files with automatic ID and timestamp generation.67 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to architect, validate, scaffold, and generate code for WTinyDB document database models and patterns.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact natively with MongoDB databases, including schema discovery, CRUD operations, aggregation pipelines, and index management via natural language.19 npmMIT
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with 4D databases via REST API, supporting authentication, schema inspection, data querying, manipulation, and ORDA function calls.6-
TDQS
Scored across 5 tools
Each tool targets a distinct operation on the JayDB store: get, put, delete, list, and health check. There is no overlap or ambiguity in what each tool does, so an agent should reliably select the right one.
All tools follow the same `jaydb_` prefix and a clear action-oriented name: get, put, delete, list, health. The naming pattern is consistent and predictable, making the tool surface easy to navigate.
Five tools is well-scoped for a key-value document store server. Each tool covers a core operation without unnecessary bloat or missing essentials.
The tool set provides full CRUD coverage through get, put, and delete, plus listing for discovery and health for operational checking. Put explicitly handles both create and update, so no lifecycle gaps are apparent.