Multi-Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional port override for the server (default: 3001) | |
| GOOGLE_CX | No | Your Google Custom Search Engine ID | |
| BRAVE_API_KEY | No | Your Brave Search API key (must be passed via MCP env, not .env) | |
| GOOGLE_API_KEY | No | Your Google API key for Custom Search | |
| TAVILY_API_KEY | No | Your Tavily API key for search | |
| SEARCH_STRATEGY | No | Search strategy to use (e.g., random or priority) | |
| SEARCH_PROVIDERS | No | Comma-separated list of providers in desired priority (e.g., tavily,google,duckduckgo,brave) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Performs a web search using multiple providers (google, tavily, duckduckgo, brave). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. Agents can reliably select the search tool for web search tasks.
With a single tool named 'search', naming is perfectly consistent within its own context. No pattern conflicts arise.
One tool is borderline for a search server. While it provides core search functionality, it is minimal and could benefit from separate tools for different providers or result handling.
The tool covers the primary search operation and abstracts multiple providers, fulfilling the server's stated purpose. Minor gaps like provider-specific parameters or result filtering are absent but not critical.