Web MCP Server

MCP web search + tiered web fetch for AI agents (Exa, Firecrawl), SSRF-guarded, cross-platform.

Local serverstdioPython

What is the Web MCP server?

Web MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP web search + tiered web fetch for AI agents (Exa, Firecrawl), SSRF-guarded, cross-platform.

What you get

An agent's stock WebSearch / WebFetch tend to flatten many sources into one blurry summary, drop provenance, and silently fail on JavaScript-heavy or anti-bot pages. This server fixes that:

What the assistant can call

Once Web is connected, these are the calls the assistant has available:

  • Safety — —
  • Cost — Bundled / metered by your model vendor
  • Provider — Free tier (verified 2026)
  • Exa1,000 requests / month, no card
  • Firecrawl1,000 pages / month, no card

Setting it up

fetches on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 2 environment variables: EXA_API_KEY, FIRECRAWL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Web's toolset — Safety, Cost, Provider and 2 more — is a fair guide to whether it matches your workflow. It is maintained by VelvetSP; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the web mcp server does with a few real requests.

Available tools

ToolWhat it does
Safety
CostBundled / metered by your model vendor
ProviderFree tier (verified 2026)
Exa**1,000 requests / month**, no card
Firecrawl**1,000 pages / month**, no card

How to install the Web MCP server

{
  "mcpServers": {
    "web-retrieval": {
      "command": "web-retrieval-mcp",
      "env": {
        "EXA_API_KEY": "exa-...",
        "FIRECRAWL_API_KEY": "fc-..."
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
EXA_API_KEYCredential the server authenticates with.Yes
FIRECRAWL_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Web to Safety.
  • Use Web to Cost.
  • Use Web to Provider.

Frequently asked questions

It connects Web to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Safety, Cost, Provider, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Web directly.