Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Local web search with multi-engine deep research and on-device re-ranking. No API keys.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
MCPSURFR_MAX_CHARSYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mcpsurfr": {
"command": "uvx",
"args": [
"mcpsurfr"
],
"env": {
"MCPSURFR_MAX_CHARS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add mcpsurfr --env MCPSURFR_MAX_CHARS=your-value -- uvx mcpsurfrFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcpsurfr": {
"command": "uvx",
"args": [
"mcpsurfr"
],
"env": {
"MCPSURFR_MAX_CHARS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mcpsurfr": {
"type": "stdio",
"command": "uvx",
"args": [
"mcpsurfr"
],
"env": {
"MCPSURFR_MAX_CHARS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MCPSURFR_MAX_CHARS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account nkapila6, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.3) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Local web search for your LLM over MCP. No API keys, and results are ranked on your machine. Formerly mcp-local-rag .
flowchart LR
Q["query + keywords"] --> S["ddgs several engines, no keys"] S --> R["re-rank on device"] R --> F["fetch top pages main text, PDFs"] F -->|search| P["best passages ~1k tokens"] F -->|rag_search_ddgs deep_research| W["full pages shared budget"]
What's in it:
auto mode asks several engines at once and skips blocked ones.search returns just the paragraphs that answer the question, about a tenth of the tokens, and deep_research can do the same per search term. When nothing matches well, search can ask you whether you want the full pages instead.truncated, and fallbacks and engine failures show up as warnings. Google blocks often, so it falls back to auto on its own.research prompt, so clients pick up how to use it without setup.| Tool | Use it for |
|---|---|
search | Start here: returns only the relevant passages. Pass keywords for better hits |
rag_search_ddgs | Full pages as text (the original mode). Takes a backend |
deep_research | Several search terms across backends, merged and de-duplicated. passages: true returns only the relevant passages per term |
read_url | One page you already have the link for. Pass a query to get only the passages that answer it |
The search tools also take recency (day, week, month, year), region (uk-en, de-de...), include_domains / exclude_domains, and news: true for dated news articles.
The old rag_search_google, deep_research_ddgs and deep_research_google presets are hidden by default. Options says why and how to turn them back on.
Backends: auto (default), brave, duckduckgo, google, grokipedia, mojeek, startpage, wikipedia, yahoo. auto and brave are the dependable ones. With news: true: auto, bing, duckduckgo, yahoo.
Other keyless MCP servers (mcp-searxng, duckduckgo-mcp-server, open-webSearch, the official fetch server) hand the model snippets or whole pages. Hosted APIs like Tavily, Exa and Brave do cut pages down to the useful parts, but they need a key and do it on their servers. mcpsurfr does that part on your machine:
What it doesn't do: JavaScript-only pages, OCR for scanned PDFs, image search.
From PyPI with uv:
{
"mcpServers": { "mcpsurfr": { "command": "uvx", "args": ["mcpsurfr"] } } }
uvx keeps using the version it cached first. Use "mcpsurfr@latest" to pick up new releases on every start (about a second slower), or "mcpsurfr@ " to pin one. uv tool install mcpsurfr works too, with "command": "mcpsurfr".
Or with Docker (amd64 and arm64):
{
"mcpServers": { "mcpsurfr": { "command": "docker", "args": ["run", "--rm", "-i", "--init", "ghcr.io/nkapila6/mcpsurfr:latest"] } } }
All settings are optional. These configs set each one to its default, so change only what you need. With uvx they go in env:
{
"mcpServers": { "mcpsurfr": { "command": "uvx", "args": ["mcpsurfr"], "env": { "MCPSURFR_MAX_CHARS": "40000", "MCPSURFR_DEEP_RESEARCH_MODE": "pages", "MCPSURFR_CACHE_TTL": "300", "MCPSURFR_LEGACY_TOOLS": "0" } } } }
| Variable | Default | What it does |
|---|---|---|
MCPSURFR_MAX_CHARS | 40000 | Text budget per call when returning full pages (rag_search_ddgs, deep_research, read_url without a query), shared across pages. ~4 chars per token |
MCPSURFR_DEEP_RESEARCH_MODE | pages | What deep_research returns when a call doesn't say: pages (full text) or passages (only what answers each term, about a tenth of the tokens) |
MCPSURFR_CACHE_TTL | 300 | Seconds searches and fetched pages are reused. 0 turns the cache off. News searches are never cached |
MCPSURFR_LEGACY_TOOLS | 0 | 1 brings back rag_search_google, deep_research_ddgs and deep_research_google, for prompts or workflows that still call them by name |
Why the legacy tools are off: they're just rag_search_ddgs and deep_research with a fixed backend, which the search tools now take themselves. Each tool's name, description and parameters get sent to the model in every chat whether it's used or not, so three duplicates cost context for nothing and give the model more ways to pick the wrong one.
With Docker, env only reaches the docker command, not the container, so the settings go in args with -e, before the image name. The same defaults:
{
"mcpServers": { "mcpsurfr": { "command": "docker", "args": [ "run", "--rm", "-i", "--init", "-e", "MCPSURFR_MAX_CHARS=40000", "-e", "MCPSURFR_DEEP_RESEARCH_MODE=pages", "-e", "MCPSURFR_CACHE_TTL=300", "-e", "MCPSURFR_LEGACY_TOOLS=0", "ghcr.io/nkapila6/mcpsurfr:latest" ] } } }
Not sure where your config lives? See the MCP quickstart. Tested with Claude Desktop, Claude Code, Cursor and Goose.
Coming from `mcp-local-rag`? Your old config keeps working, since the old URL redirects and the mcp-local-rag command still exists. Switching to the config above gets you the new name and drops the --python=3.10 pin (3.10 is end of life as of October 2026). If your prompts call rag_search_google or deep_research_google by name, set MCPSURFR_LEGACY_TOOLS to 1 (see Options).
The mcpsurfr-search skill tells the model which tool and backend to pick and how to cite. The server serves it as skill://mcpsurfr-search/SKILL.md, so most clients need nothing extra. To add it to Claude Desktop by hand: Settings → Skills → Add from folder, then pick src/mcpsurfr/skills/mcpsurfr-search/.
The research(topic) prompt plans a few search terms, runs deep_research and writes a cited summary.
Asking Claude Desktop about something newer than its training data:
Security audit by MseeP · Issues and PRs welcome · MIT licensed · Buy me a coffee if it helps you