Brave Jev MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAVE_API_KEY | Yes | Your Brave Search API key for search. Required. | |
| TYPESAFE_API_KEY | No | Your Jev API key for filtering. Optional; without it, search still works and Jev filtering is skipped. | |
| JEV_FILTER_CONFIG_FILE | No | Optional file path to store configuration elsewhere. You must create that file yourself. |
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 | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brave_web_searchA | Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata. |
| brave_local_searchA | Brave Local Search API provides enrichments for location search results. Access to this API is available only through the Brave Search API Pro plans; confirm the user's plan before using this tool (if the user does not have a Pro plan, use the brave_web_search tool). Searches for local businesses and places using Brave's Local Search API. Best for queries related to physical locations, businesses, restaurants, services, etc. |
| brave_video_searchA | Searches for videos using Brave's Video Search API and returns structured video results with metadata. |
| brave_image_searchA | |
| brave_news_searchA | This tool searches for news articles using Brave's News Search API based on the user's query. Use it when you need current news information, breaking news updates, or articles about specific topics, events, or entities. |
| brave_summarizerA | Retrieves AI-generated summaries of web search results using Brave's Summarizer API. This tool processes search results to create concise, coherent summaries of information gathered from multiple sources. |
| brave_llm_contextA | Search the web with Brave and return pre-extracted, relevance-ranked content chunks (prose, tables, code blocks, structured data). Use the returned content directly when it answers the question; fetch the page only when you need the full context or must verify. |
| brave_place_searchA | Searches Brave's Place Search API. A single call may populate any combination of 'results' (POIs), 'cities', 'addresses', 'streets', and 'location' (the resolved search area), depending on the query's shape. |
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 8 tools
Each tool targets a distinct search modality or output format (web, images, video, news, summaries, LLM context), so broad intent is usually clear. The main overlap is between brave_local_search and brave_place_search, which both return business/POI data; descriptions differentiate use cases but an agent could still misselect.
All tools use a consistent brave_ prefix and snake_case, with six following a brave_<type>_search pattern. The two exceptions (brave_summarizer, brave_llm_context) are still clearly named and predictable.
Eight tools map cleanly to Brave Search API endpoints, with no redundant or filler entries. The count is well-scoped for a search provider.
The surface covers all major Brave Search API capabilities: web, local, video, image, news, summarizer, LLM context, and place search. No obvious gap in the core search lifecycle.