Schema | Multi-Search MCP Server

Multi-Search MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`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)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
searchB	Performs a web search using multiple providers (google, tavily, duckduckgo, brave).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guptabhishek/multi-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server