web-research-mcp
The web-research-mcp server acts as a persistent, version-aware cache for web research, enabling host AI models to store, retrieve, and validate documentation without re-researching the same sources every session.
Browse the cache hierarchy: View a structured tree of cached technologies → versions → topics, including freshness flags, without fetching content.
Check freshness/existence: Quickly verify if a specific tech/topic reference is cached and current — returns status, staleness info, and slug without fetching full content.
Retrieve cached docs: Fetch complete markdown content for a cached reference by slug, or retrieve just a specific section/heading.
Full-text search: Search across topic names, summaries, content, and tags — optionally scoped to a specific technology.
Store new research: Save researched documentation (tech, topic, version, summary, content, tags, sources) into the cache; atomically supersedes older versions and warns about possible duplicate topics.
Invalidate references: Mark a cached entry as stale by slug, prompting re-research on next use.
Self-update guidance: Detect newer server versions on GitHub and return the update command, delegating execution to a background agent to avoid blocking workflow.
Enforce consultation (optional): Install a pre-edit hook requiring the host model to consult cached references before editing code for tracked technologies.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@web-research-mcpCheck if we have React server components documentation cached."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
web-research-mcp
An MCP server that keeps a persistent, version-aware cache of web research so the host model (Claude, Codex, …) writes modern, non-deprecated code without re-researching the same docs every session.
The server never browses the web itself — the host does the searching when the user asks. This server only stores what was found, answers "do we already have this? is it current?" cheaply, and serves the cached reference back.
Install
One line — no clone needed:
curl -LsSf https://raw.githubusercontent.com/jcsoftdev/web-research-mcp/main/install.sh | bashOr from a checkout:
./install.shInteractive: installs uv if missing, installs the web-research-mcp binary, then
asks which hosts to register into (Claude Code, Codex, Gemini, Claude Desktop,
Cursor) and wires each one up. The DB autocreates on first use.
Manual registration
# Claude Code
claude mcp add web-research -s user -- web-research-mcp
# Codex
codex mcp add web-research -- web-research-mcpOther hosts (JSON config):
{
"mcpServers": {
"web-research": { "command": "web-research-mcp", "args": [] }
}
}Related MCP server: Context7 MCP
Tools
Tool | Cost | Behavior |
| minimal | Hierarchy tech → version → topics (names + |
| low |
|
| med-high | Full markdown doc; optional section returns one heading block. |
| med | FTS5 over topic + summary + content + tags. |
| write | Stores a doc; atomically supersedes older versions (PEP 440 compare). |
| write | Forces a reference stale. |
Freshness is a structured field (status_tag, stale) placed first in every
response, and a stale entry carries an explicit advice field — the model can't
overlook deprecation buried in prose. A cache miss is a flat {"exists": false}.
Dedup gate
save_research guards against forking the same concept under different topic
names (server-components vs servercomponents). Before inserting it looks for
similar existing topics for that tech and, if any, returns them in a
possible_duplicates field so the host reuses an existing slug instead of
creating a duplicate. It is advisory, non-blocking. Matching is lexical today
(near-spellings, spacing, truncated abbreviations); synonyms and non-truncation
abbreviations (rsc vs server-components) need embeddings, which swap in at the
same call site via EmbeddingProvider when EMBEDDINGS_ENABLED=1.
Enforcement hook (optional)
The MCP instructions only ask the model to call check_reference before
writing code — nothing enforces it. The installer can wire a host pre-edit
hook that turns the ask into a guarantee: if you are about to edit code for a
cached tech and the current session never consulted its reference, the edit is
denied until you do.
web-research-mcp hook --host {claude|codex|gemini|cursor}The hook reads the host's pre-edit event on stdin, detects tracked techs in the
edit via strong signals only (real JS/TS imports or package.json dependency
keys — never prose), and checks the session transcript for a prior
check_reference / get_reference call. Detection is conservative by design: a
false deny blocks a legitimate edit.
Install is opt-in (default no) because a deny is disruptive. Support:
host | event | status |
Claude Code |
| verified |
Codex |
| experimental |
Gemini CLI |
| experimental (schema unverified) |
Cursor |
| experimental |
The hook fails open: any parse error, unknown host, or unreadable DB allows the edit — a bug in the gate must never wedge your editor.
Config (env vars)
var | default | purpose |
|
| DB location (global — reused across projects) |
|
| TTL for non-version-locked entries |
|
| vector search (post-MVP) |
|
| advertise updates so the host auto-delegates them; set |
Auto-update
The server never installs anything itself. It exposes a check_for_update tool
and, via its MCP instructions, asks the host to delegate a background agent to
run the update when a newer version exists on GitHub — so the update never blocks
you and takes effect on the next launch. The host does the work; the server only
detects and advises.
With WEB_RESEARCH_AUTO_UPDATE=0 the tool still exists but the instructions no
longer ask the host to auto-delegate — call check_for_update yourself when you
want it.
Develop
uv sync
uv run pytestMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jcsoftdev/web-research-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server