Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NAME | No | Server name override | url-context-mcp |
| SEARCH_MCP_API_KEY | No | Your API key (if applicable) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Search the web using Brave Web Search API |
| local_poisC | Fetch extra information for locations using Brave Local Search API |
| local_descriptionsC | Fetch AI-generated descriptions for locations using Brave Local Search API |
| rich_fetchC | Fetch rich results using the callback_key from web_search |
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 4 tools
The tools have some overlap in purpose, particularly between local_descriptions and local_pois, which both fetch location information using the same API and could be confused. However, web_search and rich_fetch are distinct in targeting general web search and rich results respectively, and the descriptions help clarify the differences.
The naming is mostly consistent with a clear pattern of using descriptive terms like 'local', 'web', and 'rich', all in snake_case. The only minor deviation is that rich_fetch uses 'fetch' while others use more specific verbs like 'search' or 'descriptions', but overall the pattern is readable and predictable.
With 4 tools, this server is well-scoped for a search-focused purpose, covering local descriptions, local points of interest, rich results, and general web search. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool surface covers key search operations for both web and local domains, with minor gaps such as no explicit tool for image or news search, but agents can likely work around this using the provided tools. The inclusion of rich_fetch as a callback from web_search adds useful functionality.