Rag MCP Server

Connect Rag to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Repository intelligence, code graph, history, papertrail, and cross-agent memory for coding agents. The rag mcp server is what makes that connection.

What the server does

Explore the live VS Code Lens demo — no installation required. It surfaces clone classes, repo memories, and issue/decision context alongside the code; press Ctrl+Alt+R to reveal clone overlays.

• Provenance, not guesses. — Every result carries a confidence label, coverage warnings, and the
• Repo memories. — Typed, source-anchored notes (Invariant, Decision, Risk, …) that survive
• A real code graph. — tree-sitter callers/callees/imports across Rust, TypeScript/TSX, Kotlin,
• History as evidence. — Git history, lazy chunk blame, and cached GitHub issue/PR/review
• Issue distillation. — Every closed issue and merged PR plus its fixing diff distilled into a typed
• Rides your existing grep. — A grep-augmentation hook injects the

Installation

The server ships on npm as @rag-rat/skills, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: LENS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by cq27-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.