Earch MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NAME | No | Server name override | earch-mcp |
| BRAVE_API_KEY | No | Your Brave API key (alternative to EARCH_MCP_API_KEY) | |
| EARCH_MCP_API_KEY | No | Your API key for Earch MCP (or BRAVE_API_KEY) |
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 | Brave Web Search: returns results for query q |
| local.poisC | Brave Local Search POIs: fetch extra info for up to 20 location ids |
| local.descriptionsC | Brave Local Search AI descriptions: fetch descriptions for up to 20 location ids |
| web.richC | Brave Rich Search via callback flow. First enables rich callback, then fetches rich data |
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 are mostly distinct in purpose, with clear separation between local search (descriptions vs. POIs) and web search (rich vs. standard). However, the distinction between 'local.descriptions' and 'local.pois' could be slightly ambiguous without more context about what each returns, as both handle location IDs.
Naming is mostly consistent with a clear prefix pattern (local. vs. web.) and descriptive suffixes. Minor deviations exist, such as 'web.rich' being less conventional than 'web.search', but overall the naming is predictable and readable.
With 4 tools, the count is well-scoped for a search-focused server. Each tool appears to serve a specific function without redundancy, making the set manageable and appropriate for the domain of search operations.
The toolset covers basic search functionalities (local and web), but there are notable gaps. For example, there is no tool for updating or deleting search data, and advanced features like filtering or sorting are missing, which could limit agent workflows in a comprehensive search domain.