
Ravendb Mcp
io.github.ravendbPublished by GitHub account ravendbv1.0.4Updated Oct 24, 2026
Read-only MCP diagnostics server for RavenDB.
Overview
Local, read-only MCP diagnostics server for RavenDB that lets an assistant inspect cluster, database, index, task, storage and performance state.
- What you can do
- Inspect cluster and server state: overview, configuration, resources, network details, notifications and compare-exchange
- Review databases: list databases, database records, stats and configuration
- Examine indexes, tasks, live workload and storage, and sample the live feed
- Read data: fetch documents and run paged RQL queries, with version-aware RQL docs as resources
- Collect diagnostics: export server logs and debug packages to local artifact files, and wait for completion of operations
- When to use it
- Useful when you want an AI agent to help diagnose a RavenDB cluster or database — checking indexes, tasks, storage, performance or query results — without giving it write access. Suited to developers and operators who already run RavenDB and want read-only inspection from their assistant.
- Requirements
- Runs locally via npx (Node.js), dnx (.NET SDK) or a prebuilt binary; a Claude Desktop extension package is also offered. Requires RAVENDB_URLS with the cluster node URLs. For secured HTTPS clusters, a client .pfx certificate via RAVENDB_CERTIFICATE_PATH and RAVENDB_CERTIFICATE_PASSWORD. Optional RAVENDB_ARTIFACTS_PATH sets where exports are written. One instance targets one cluster.
Installation
In SourceWeft
- Open Ravendb Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
RavenDB MCP
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.
Quick start
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.
Features
Developer experience
- One-line install with
npx,dnx, or a prebuilt binary. - 21 tools, one per subject area, each with parameters to select what you need (reduced from 74).
- Version-aware RQL docs are served as
rql://resources; a failed query returns the parser error and where to look.
Safety
- Read-only: no write, patch, or delete tools, and mutating queries are rejected.
- Connection-string secrets (passwords, cloud keys, SAS tokens, AI-provider keys, certificates) are masked in the returned JSON.
- Access is scoped to the client certificate's RavenDB permissions.
get_document_dataandrun_queryreturn real cluster data into the agent's context — you choose which cluster to expose. See SECURITY.md.
Context-window friendly
- Progressive disclosure: tools return an overview by default and drill into detail on request.
- Results are paged:
run_querytakesstartandpageSize(up to 128 rows), and the list tools takepageSize. - Log exports and debug packages are written to an artifact file on disk; the tool returns its path and byte size, not the contents.
- Query results omit per-document metadata unless you request it.
Runs anywhere
- Distributed via npm, NuGet, GitHub Releases, and the MCP Registry.
- Self-contained binaries for Windows, macOS, and Linux (x64 and arm64), with no runtime to install.
- Run a separate instance per cluster for multi-cluster setups.
Configuration
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:
Full configuration reference, including secured clusters and multi-cluster setups, is in INSTALL.md.
Tools
21 read-only tools (snake_case). Most are facet tools: one per subject that takes selectors and returns only the sections you ask for.
- Facets:
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_agents - Singletons:
list_databases,get_database_record,get_notifications,run_query,list_compare_exchange,export_server_logs
Large or binary output (logs, debug packages) is written to a file and returned as a reference.
Privacy
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.
License
MIT. See LICENSE. Building from source is covered in INSTALL.md.
mcp-name: io.github.ravendb/ravendb-mcp
Source: README.md at commit 648417b
Tools
0Version history
1- v1.0.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
