# @ruvector/rvf-mcp-server [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ruvnet/RuVector  
**GitHub Stars:** 4685  
**npm Downloads (last month):** 1698  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ruvector-rvf-mcp-server

## Description
MCP server for local vector search over portable RVF files: Claude Code, Cursor and other MCP clients create, fill and query HNSW-indexed .rvf stores over stdio or SSE.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "rvf-mcp-server": {
    "command": "npx",
    "args": ["-y","ruvector"],
    "env": {
      "RUVECTOR_MCP_PROFILE": ""
    }
  }
}
```

**Requires environment variables:** `RUVECTOR_MCP_PROFILE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What @ruvector/rvf-mcp-server does

@ruvector/rvf-mcp-server gives MCP clients access to local vector stores saved as portable RVF files. Agents can create stores, add records, and run vector queries against HNSW indexes. The local storage model suits project memory, semantic retrieval, and other workflows where vector data should remain available in the project environment.

The server is part of the `ruvector` npm package. It is intended for MCP-compatible agent applications, including Claude Code and Cursor. Its tools can be exposed over standard input/output or through SSE, depending on how the server is launched and connected.

## How it works

An MCP client starts the server process and communicates with it using the selected transport. For a local stdio setup, the client launches `npx` with `ruvector mcp start`. The project directory acts as the working directory, allowing the server to use the associated local RuVector data.

The package includes an MCP tool inspection command, `npx ruvector mcp tools`, which can be used before connecting a client. A read-only operating profile is available through the `RUVECTOR_MCP_PROFILE` environment variable. Write access is intended to be enabled deliberately through an explicit tool policy rather than assumed by the client.

## Setup and configuration

Install Node.js and npm, then use the `ruvector` package through `npx` or install it in the project. A basic read-only launch is:

```bash
RUVECTOR_MCP_PROFILE=readonly npx ruvector mcp start
```

Configure the MCP client to run `npx` with the arguments `ruvector mcp start`, set the working directory to the project, and pass the profile environment variable when needed. Claude Code can register a project-scoped stdio connection with:

```bash
claude mcp add --scope project --env RUVECTOR_MCP_PROFILE=readonly --transport stdio ruvector -- npx -y ruvector mcp start
```

After registration, use the client's MCP status or connection view to verify that the server is available. Keeping the npm lockfile in the project helps preserve the selected dependency version.

## Tools and capabilities

- Inspect the available MCP tools before connecting an agent.
- Create local RVF vector stores.
- Fill stores with records for later retrieval.
- Query HNSW-indexed vector data.
- Expose local vector search through stdio or SSE.
- Apply a read-only profile for safer agent access.

## Limitations and notes

The server depends on a local Node.js and npm environment. Semantic text workflows also require an embedding model; the first semantic command in the broader `ruvector` package downloads a local model. Retrieved records should be treated as project evidence and checked against current source files when used as agent memory.

Write operations should be governed explicitly through the MCP client's tool policy. A read-only profile is the documented starting point for connecting an agent, while populating memory can be performed separately through the npm-based RuVector workflow or an intentionally enabled write policy.

_Full upstream README: https://allmcps.com/mcp/ruvector-rvf-mcp-server/readme_