ravendb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAVENDB_URL | Yes | URL of the RavenDB server (e.g., http://your-ravendb-server:port). | |
| RAVENDB_AUTH_METHOD | Yes | Authentication method. Only non-secured mode is supported, set to 'none'. | |
| RAVENDB_QUERY_TIMEOUT | No | Query timeout in milliseconds (optional, default 30000). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize-connectionC | Connect to a RavenDB server |
| select-databaseB | Switch to a specific database context |
| show-collectionsA | List available collections in the current database |
| show-indexesA | List available indexes in the current database |
| get-documentB | Retrieve a document by ID |
| store-documentB | Create or update a document |
| delete-documentB | Delete a document by ID |
| query-documentsC | Execute RQL queries with results handling |
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 8 tools
Each tool targets a distinct operation: CRUD on documents, connection management, database selection, and metadata listing. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern with lowercase and hyphens (e.g., delete-document, get-document, show-collections). No mixing of styles.
8 tools is well-scoped for a RavenDB server: core CRUD, query, connection setup, database selection, and metadata listing. Not excessive or insufficient.
Covers basic document operations (create/read/delete), query, connection, and metadata. Missing explicit index management and bulk operations, but core workflows are complete.