Codeloupe MCP

codeloupe-mcp

A Model Context Protocol (MCP) server that gives coding agents fast, local-first access to large codebases. It enables LLMs to inspect files, search text, compare directories, read symbols, and apply structured edits through bounded tool responses instead of dumping whole files or repository trees into context.

codeloupe-mcp vs shell tools

This package provides an MCP interface into repository exploration and code editing.

If you are using a coding agent, shell commands are still useful for concise build/test workflows. codeloupe-mcp is most useful when the model needs structured, repeatable, repository-aware code context across a chat session.

• Shell / CLI: best for deterministic commands such as cargo test, npm run lint, project scripts, one-off rg, and build logs that are already compact.
• MCP: best for agent loops that benefit from tool schemas, workspace-aware path resolution, bounded output, persistent indexes, and precise reads such as symbol bodies, snippets, shallow project maps, and directory diffs.

Use codeloupe-mcp when you want an agent to ask for exactly the code context it needs: a line range, a symbol body, a bounded search result, a fuzzy file match, a workspace summary, or a source-directory comparison.

Key Features

• Fast and lightweight. Local Rust server over stdio; no external indexing service, no network calls, no telemetry.
• LLM-friendly output. Tools return bounded JSON/Markdown designed for agent context windows.
• Repository-aware indexing. LMDB path metadata plus optional Tantivy content indexing per workspace.
• Precise code reads. Read focused line ranges, snippets, symbol bodies, imports, exports, call graphs, definitions, and references.
• Scoped search. Literal and regex search with path scopes, include/exclude globs, fallback diagnostics, and large-repo safeguards.
• Directory comparison. Compare two source directories with added/deleted/modified/renamed summaries and bounded diffs.
• Structured edits. Create, edit, convert, delete, batch-edit, and undo files with predictable success/error metadata.

Requirements

• An MCP client that supports local stdio servers.
• Node.js 18 or newer when using npx.
• No Rust toolchain is needed when using the published npm package or a native release binary.
• Rust 1.98.1 is required only when building from source; rust-toolchain.toml installs the pinned toolchain through rustup.

Getting started

First, install the codeloupe-mcp server with your client.

Standard config works in most MCP clients:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

You can also use a native binary from the GitHub Releases page:

{

"mcpServers": { "codeloupe-mcp": { "command": "/absolute/path/to/codeloupe-mcp", "args": [] } } }

On Windows native installs, point command to the .exe file, for example C:\path\to\codeloupe-mcp.exe.

Amp

Add via the Amp VS Code extension settings screen or by updating your settings JSON:

"amp.mcpServers": {

"codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } }

Amp CLI setup:

amp mcp add codeloupe-mcp -- npx -y @ndhkaeru/codeloupe-mcp@latest

Antigravity

Add via Antigravity settings or by updating your MCP configuration file:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Claude Code

Use the Claude Code CLI:

claude mcp add codeloupe-mcp -- npx -y @ndhkaeru/codeloupe-mcp@latest

Native binary alternative:

claude mcp add codeloupe-mcp -- /absolute/path/to/codeloupe-mcp

Claude Desktop

Follow the MCP install guide and use the standard config:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Native Windows binary alternative:

{

"mcpServers": { "codeloupe-mcp": { "command": "C:\\path\\to\\codeloupe-mcp.exe", "args": [] } } }

Cline

Follow Cline's MCP server configuration flow and add this to cline_mcp_settings.json:

{

"mcpServers": { "codeloupe-mcp": { "type": "stdio", "command": "npx", "timeout": 60, "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"], "disabled": false } } }

Codex

Use the Codex CLI:

codex mcp add codeloupe-mcp -- npx -y @ndhkaeru/codeloupe-mcp@latest

Alternatively, create or edit ~/.codex/config.toml:

[mcp_servers.codeloupe-mcp]

command = "npx" args = ["-y", "@ndhkaeru/codeloupe-mcp@latest"]

Copilot

Use the Copilot MCP add flow, or add this to your MCP config:

{

"mcpServers": { "codeloupe-mcp": { "type": "local", "command": "npx", "tools": ["*"], "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Cursor

Go to Cursor Settings -> MCP -> Add new MCP Server.

Use command type with:

npx -y @ndhkaeru/codeloupe-mcp@latest

Or paste the standard config:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Factory

Use the Factory CLI:

droid mcp add codeloupe-mcp "npx -y @ndhkaeru/codeloupe-mcp@latest"

Alternatively, open Factory's MCP UI and paste the standard config.

Gemini CLI

Use the Gemini CLI MCP configuration file and add:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Goose

Go to Advanced settings -> Extensions -> Add custom extension.

Use type STDIO and command:

npx -y @ndhkaeru/codeloupe-mcp@latest

Junie

Use Junie's MCP flow, or add to .junie/mcp/mcp.json:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Kiro

Follow Kiro's MCP server documentation and add:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

LM Studio

Go to Program in the right sidebar -> Install -> Edit mcp.json.

Use the standard config:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

opencode

Add to ~/.config/opencode/opencode.json:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "codeloupe-mcp": { "type": "local", "command": ["npx", "-y", "@ndhkaeru/codeloupe-mcp@latest"], "enabled": true } } }

Qodo Gen

Open Qodo Gen chat panel in VS Code or IntelliJ, choose Connect more tools -> + Add new MCP, then paste the standard config.

VS Code

Use the MCP server configuration:

{

"servers": { "codeloupe-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

You can also install with the VS Code CLI:

code --add-mcp '{"name":"codeloupe-mcp","command":"npx","args":["-y","@ndhkaeru/codeloupe-mcp@latest"]}'

Warp

Go to Settings -> AI -> Manage MCP Servers -> + Add, or use the /add-mcp slash command and paste the standard config.

Windsurf

Follow Windsurf's MCP documentation and use the standard config:

{

"mcpServers": { "codeloupe-mcp": { "command": "npx", "args": ["-y", "@ndhkaeru/codeloupe-mcp@latest"] } } }

Configuration

codeloupe-mcp accepts repeatable --workspace / --workspace= arguments and environment variables in the MCP server process. Explicit CLI and environment workspaces are approved for indexing unless index mode is off. --help and --version print immediately without starting the stdio server; unknown CLI options fail instead of silently starting it.

After upgrading the server, reconnect or restart the MCP client so it fetches the current tools/list schema. Long-running clients such as Claude Code can keep the previous session's tool parameters until they reconnect.

Legacy codeloupe_mcp_* and CODEBASE_MCP_* names remain supported for compatibility; the uppercase CODELOUPE_MCP_* names take precedence.

On Windows, the npm launcher copies the native binary to %LOCALAPPDATA%\codeloupe-mcp\runtime\ - \ and runs that copy. Windows locks running executables, so running directly from `node_