mcp-local-rag

What this does

mcp-local-rag exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

BASE_DIR
BASE_DIRS
DB_PATH
CACHE_DIR
MODEL_NAME
MAX_FILE_SIZE
RAG_MAX_DISTANCE
RAG_GROUPING
RAG_MAX_FILES
CHUNK_MIN_LENGTH
RAG_DEVICE
RAG_DTYPE
RAG_HYBRID_WEIGHT
RAG_WATCH
HF_ENDPOINT
HF_AUTO_MIRROR
HTTPS_PROXY
HTTP_PROXY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install mcp-local-rag?

Run the Claude Code command in the install section to add mcp-local-rag to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with mcp-local-rag?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to mcp-local-rag as well.

Does mcp-local-rag need an API key?

This listing does not flag an API key as required. The server can use these environment variables: BASE_DIR, BASE_DIRS, DB_PATH, CACHE_DIR, MODEL_NAME, MAX_FILE_SIZE, RAG_MAX_DISTANCE, RAG_GROUPING, RAG_MAX_FILES, CHUNK_MIN_LENGTH, RAG_DEVICE, RAG_DTYPE, RAG_HYBRID_WEIGHT, RAG_WATCH, HF_ENDPOINT, HF_AUTO_MIRROR, HTTPS_PROXY, HTTP_PROXY; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.