Web MCP Server

Your AI research assistant that cites real sources and stays honest — web search, content extraction, and multi-source research over MCP. The web mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

Configuration

You will need 8 environment variables: GOOGLE_CUSTOM_SEARCH_API_KEY, GOOGLE_CUSTOM_SEARCH_ID, SEARCH_PROVIDER, BRAVE_API_KEY, FRED_API_KEY, YOUR_KEY, YOUR_GOOGLE_API_KEY, YOUR_SEARCH_ENGINE_ID. 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.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

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. It is maintained by Zohar Babin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Web's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• 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.