@jaydb/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JAYDB_URL | No | Base URL of JayDB Cloud tenant or local JayDB instance | http://localhost:8080 |
| JAYDB_API_KEY | No | Server-side API key (X-JayDB-API-Key) | |
| JAYDB_NAMESPACE | No | Default document namespace/bucket | default |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jaydb_getA | Retrieve a document by key from JayDB or JayDB Cloud |
| jaydb_putA | Create or update a document with optimistic concurrency control (CAS) |
| jaydb_deleteC | Delete a document from JayDB or JayDB Cloud |
| jaydb_listA | List keys and metadata by prefix in JayDB or JayDB Cloud |
| jaydb_healthA | Check connectivity and health of the JayDB endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.