The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Ravendb MCP listing page.
A local, read-only MCP diagnostics server for RavenDB. Point it at a cluster and your AI agent can inspect cluster, database, index, task, storage, and performance state, plus logs, support packages, and your data, across 21 read-only tools.
Launch it with npx (Node.js), dnx (.NET SDK), or a prebuilt binary from Releases, then add it to your client. Set RAVENDB_URLS to your cluster; the examples use http://localhost:8080.
Claude Code
Or install the plugin, which prompts for your cluster URL:
Claude Desktop
Download ravendb-mcp-<version>.mcpb from Releases, then install it under Settings > Extensions > Advanced settings > "Install Extension…" (Anthropic's guide). It prompts for your cluster URL, so there is no config to edit and no Node or .NET needed. Config-file setup is in INSTALL.md.
Codex
Add to ~/.codex/config.toml:
Cursor
Click the button (installs with http://localhost:8080; edit for another cluster), or add .cursor/mcp.json:
Then ask the agent “list my RavenDB databases.” Any of these can use dnx RavenDB.Mcp --yes or a binary path in place of npx -y @ravendb/mcp. Secured (HTTPS) clusters, other OSes, and the full configuration reference are in INSTALL.md.
Developer experience
npx, dnx, or a prebuilt binary.rql:// resources; a failed query returns the parser error and where to look.Safety
get_document_data and run_query return real cluster data into the agent's context — you choose which cluster to expose. See SECURITY.md.Context-window friendly
run_query takes start and pageSize (up to 128 rows), and the list tools take pageSize.Runs anywhere
One server instance targets one cluster. The only required setting is the URL; pass it (and the optional certificate / artifacts settings) as environment variables or a --config JSON file:
| Variable | Required | Purpose |
|---|---|---|
RAVENDB_URLS | yes | Cluster node URL(s), comma-separated, the client fails over across them. |
RAVENDB_CERTIFICATE_PATH / _PASSWORD | no | Client .pfx for secured (HTTPS) clusters. Omit for unsecured. |
RAVENDB_ARTIFACTS_PATH | no | Where exported files are written (defaults to a temp folder). |
Full configuration reference, including secured clusters and multi-cluster setups, is in INSTALL.md.
21 read-only tools (snake_case). Most are facet tools: one per subject that takes selectors and returns only the sections you ask for.
get_cluster_overview, get_server_config, get_server_resources, get_network_details, get_database_stats, get_database_config, get_index, get_tasks, get_live_workload, inspect_storage, get_document_data, sample_live_feed, wait_for_completion, collect_debug_package, get_ai_agentslist_databases, get_database_record, get_notifications, run_query, list_compare_exchange, export_server_logsLarge or binary output (logs, debug packages) is written to a file and returned as a reference.
RavenDB MCP runs locally and sends no data to RavenDB or Anthropic: no telemetry, no analytics. It connects only to the cluster URL(s) you configure (and to npm/NuGet when you install via npx/dnx), returns results to your local agent, masks connection-string secrets, and writes exports only to a local folder you control. Details in PRIVACY.md; RavenDB's company policy is at ravendb.net.
MIT. See LICENSE. Building from source is covered in INSTALL.md.
mcp-name: io.github.ravendb/ravendb-mcp