MCP Web Search Tool MCP Server

MCP Web Search Tool — Model Context Protocol server providing real-time web search, news, image search, and URL content extraction with pluggable providers (Brave, DuckDuckGo). That is what the mcp web search tool mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP server that gives an assistant live web search, full-page reading, and source citations. Stdio transport, pluggable providers, no scraper dependencies.

Five tools: web_search, news_search, image_search, fetch_url, list_providers. Search returns ranked summaries with stable ids; fetch_url reads the page behind any id. Brave Search is the primary provider; DuckDuckGo runs without a key as a fallback.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 5 tools. What each one is for:

• web_search — Live web search. Use first for current, source-backed answers
• news_search — The news_search tool exposed by this server
• image_search — The image_search tool exposed by this server
• fetch_url — Reads a search result or arbitrary http(s) URL. Pass a result id from a previous search (preferred) or a full URL
• list_providers — Returns the registered providers and the current default. Call this once if you are unsure whether news_search or image_search are available in this

What it needs from you

Configuration is passed through the environment: BRAVE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

| | | |---|---| | Node.js | >= 20.18 (uses native fetch) | | npm | >= 10 | | Brave Search API key | optional. Without it, DuckDuckGo handles web_search. news_search and image_search require a key. |

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of search and retrieval servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Web Search Tool's toolset — web_search, news_search, image_search and 2 more — is a fair guide to whether it matches your workflow. It is maintained by gabrimatic; 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.