@greatnxy/web-search-mcp
Provides web search functionality through the Brave Search API, returning ranked results with titles, URLs, and snippets. It is used as a fallback provider when Tavily is unavailable or returns no results.
Click on "Deploy 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., "@@greatnxy/web-search-mcp what are the latest developments in renewable energy?"
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.
@greatnxy/web-search-mcp
A focused MCP server that gives your MCP client a straightforward way to search the web and receive structured results through a single tool: web_search.
This server integrates with Tavily and Brave because both services provide free usage options, making it practical to get started with web search. See their plans and pricing: Tavily Plans & Pricing · Brave Search API Plans.
Install and run
npm install
$env:TAVILY_API_KEY = "tvly-..."
$env:BRAVE_API_KEY = "BSA..."
npm run build
npm startIf you want to use only Brave's free quota, be sure to set a usage limit for your Brave Search account. Configure it inBrave Search usage limits.
For key rotation within each provider, use comma-separated values.
$env:TAVILY_API_KEYS = "tvly-first,tvly-second"
$env:BRAVE_API_KEYS = "brave-first,brave-second"Keys are chosen randomly from each provider's currently available pool. A 429 pauses that Key until the provider's response says it can be retried. An authentication or quota error removes the Key until the server is restarted.
Related MCP server: AIE7-MCP
VS Code configuration
Create or edit your MCP configuration and keep secrets in password inputs:
{
"inputs": [
{
"type": "promptString",
"id": "tavily-api-key",
"description": "Tavily API key",
"password": true
},
{
"type": "promptString",
"id": "brave-api-key",
"description": "Brave Search API key",
"password": true
}
],
"servers": {
"web-search": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@greatnxy/web-search-mcp"],
"env": {
"TAVILY_API_KEY": "${input:tavily-api-key}",
"BRAVE_API_KEY": "${input:brave-api-key}"
}
}
}
}Environment variables
Variable | Default | Purpose |
| required | One key or a comma-separated Tavily key pool. |
| required | One key or a comma-separated Brave key pool. |
|
| Tavily and Brave HTTP request timeout. |
Search behavior
The gateway calls Tavily first. It calls Brave when Tavily returns no results, times out, is unavailable, is rate-limited, or reports exhausted plan/PAYG quota. Each request randomly selects an available key from the chosen provider's pool.
Tool input and output
web_search accepts query, optional max_results (1–20), freshness (day, week, month, year), ISO country code, and include/exclude domain lists.
It returns query, selected provider, fallback state and reason, providers tried, and ranked title/url/snippet results.
Verify
npm run check
npm test
npm run buildAvailable Tools
1 toolweb_searchA
Search the web. Tavily is used first; Brave is used only when Tavily is unavailable, out of quota, rate-limited, or returns no results.
Inputs: query (required), country, freshness, max_results, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion between tools. The purpose of the server is unambiguous.
The single tool name 'web_search' follows a clear verb_noun pattern, consistent and self-explanatory.
With only one tool, the server is minimal but might feel thin for broader search needs. However, for a focused web search purpose, it is acceptable.
For a web search server, the single tool covers the essential functionality of searching the web. There are no obvious gaps for the stated purpose.
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
Web search and clean-text fetch MCP server (Tavily-powered, SSRF-guarded).
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Free web search for AI agents. No API key required. Hosted MCP in active development.
Related MCP Servers
- AlicenseBqualityDmaintenanceA local MCP server that exposes Tavily search as a tool and rotates across multiple API keys for reliability.1MIT
- FlicenseAqualityDmaintenanceMCP server that provides web search capabilities using the Tavily API.3-
- AlicenseBqualityDmaintenanceMCP server providing search, extract, map, and crawl tools powered by Tavily for real-time web data access.440 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that gives AI agents access to current web information through web_search and fetch_url tools, using Tavily, Brave, and DuckDuckGo providers with automatic fallback.MIT