Ravendb MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

const result = spawnSync(binaryPath, process.argv.slice(2), { stdio: 'inherit' });

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

const result = spawnSync(binaryPath, process.argv.slice(2), { stdio: 'inherit' });

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

const binaryPath = path.join(__dirname, 'bin', target.rid, target.bin);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ravendb-mcp -e 'RAVENDB_URLS=<RAVENDB_URLS>' -- npx -y @ravendb/mcp

{
  "mcpServers": {
    "ravendb-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ravendb/mcp"
      ],
      "env": {
        "RAVENDB_URLS": "<RAVENDB_URLS>"
      }
    }
  }
}

[mcp_servers.ravendb-mcp]
command = "npx"
args = ["-y", "@ravendb/mcp"]
env = { RAVENDB_URLS = "<RAVENDB_URLS>" }

{
  "mcpServers": {
    "ravendb-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ravendb/mcp"
      ],
      "env": {
        "RAVENDB_URLS": "<RAVENDB_URLS>"
      }
    }
  }
}

{
  "servers": {
    "ravendb-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ravendb/mcp"
      ],
      "env": {
        "RAVENDB_URLS": "<RAVENDB_URLS>"
      }
    }
  }
}

Put your own value in place of <RAVENDB_URLS> (Comma-separated RavenDB node URLs of a single cluster, e.g. https://a.example:443,https://b.example:443). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: RAVENDB_CERTIFICATE_PATH (Path to a client .pfx certificate for secured RavenDB. Leave empty for unsecured), RAVENDB_CERTIFICATE_PASSWORD (Password for the client .pfx certificate), RAVENDB_ARTIFACTS_PATH (Directory where exported artifacts (logs, packages, dumps) are written).