Brave Jev MCP
Provides web search and content extraction through the Brave Search API, returning filtered snippets and source links for AI to read, answer, and cite.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Brave Jev MCP search for Postgres vs SQLite for a small app, with sources"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Brave Jev MCP
English | 简体中文
Web search results often contain junk articles and passages that mention the right keywords without answering the question. This material consumes context and leaves the AI to find answers among unrelated information.
This project removes unhelpful pages and snippets before search results reach the AI, leaving more context for information that can help answer the question.
Built on Brave Search MCP Server, the project uses Brave to search the web and extract content, and Jev to filter it according to the purpose of the search. Retained content keeps its source links and Brave's original ordering so the AI can read, answer, and cite it.
Filtering currently applies only to brave_llm_context. Other search tools remain available, but their results do not pass through this project's filtering layer or call Jev for screening.
Regular web search (brave_web_search) mainly returns links and short summaries that help people decide which pages to open. In contrast, brave_llm_context provides content snippets extracted from web pages for the AI to read directly. In our testing, brave_llm_context delivers significantly higher information density and more material that can directly support an answer. We therefore recommend brave_llm_context even with filtering disabled.
Installation
Prepare the following:
A Brave Search API key. A credit card is required. The API provides $5 in free monthly credits, covering 1,000 searches at the current Search plan price.
A Jev API key for filtering.
We recommend setting BRAVE_API_KEY (your Brave key) and TYPESAFE_API_KEY (your Jev key) as environment variables and ensuring that your AI client passes them to the MCP process. The server reads these variables automatically. If your client requires explicit forwarding, use its environment variable settings.
Add the following configuration to your AI client. npx downloads and starts the package automatically:
{
"mcpServers": {
"brave-jev": {
"command": "npx",
"args": [
"-y",
"@romantcig/brave-jev-mcp@latest",
"--transport",
"stdio",
"--enabled-tools",
"brave_llm_context"
]
}
}
}The example uses @latest to get the latest version published on npm.
--enabled-tools selects which tools are exposed to the AI. The configuration above exposes only brave_llm_context. To enable more tools, append their names as separate strings after this argument. If no other tool filtering options are set, removing the argument and its tool names exposes all tools.
Other tools include:
Web search (
brave_web_search): mainly returns page links and short summaries, with significantly less detailed content thanbrave_llm_context.Local search (
brave_local_search): searches for local businesses and places.News search (
brave_news_search): searches recent news articles, supports recency filters, and provides breaking news indicators.Place search (
brave_place_search): searches for businesses, places, addresses, and streets using place names or coordinates.AI summaries (
brave_summarizer): calls the legacy Summarizer API and requires an existing Pro AI plan subscription. Brave has introduced Answers API as its replacement, but this tool has not integrated it.Video search (
brave_video_search).Image search (
brave_image_search).
On first launch, the server creates ~/.brave-jev/config.json with filtering enabled by default. Existing configuration is preserved. The Brave key is required for search. Without a Jev key, search still works, Jev filtering is skipped, and results that would otherwise be filtered include setup instructions.
The MCP server loads its startup arguments, environment variables, filtering configuration, and program version at startup. Restart it for changes to take effect.
Related MCP server: groundlink-mcp
Usage
Tell the AI what you need to find. For example:
Use Brave MCP's
brave_llm_contextto compare SQLite and PostgreSQL. I am choosing a database for a single-machine application. Focus on deployment complexity, concurrent write limits, and suitable use cases, and include sources.
When choosing a database for a single-machine application, concurrency limits and deployment methods are useful; a generic passage about why choosing a database matters contributes little. With Jev filtering enabled, the AI sends search keywords and search intent separately to the tool. You only need to describe what you need.
Default search budgets
To prevent excessive output when the AI omits explicit limits, and to keep sources repeating the same information from filling the context, brave_llm_context uses these defaults:
Parameter | Default | Meaning |
| 10 | Candidate search results considered when selecting context |
| 4000 | Approximate total token budget |
| 800 | Token budget per source |
| 5 | Maximum number of returned sources |
These defaults apply in every filtering mode. Adjust the relevant parameters when calling the tool if you need more sources or detail. count is the number of candidate results, not the number of sources ultimately returned.
Search results first pass through local cleanup rules, then go to Jev for screening against the search intent. If the Jev key is missing or the Jev request fails, the MCP server still returns the content after local cleanup, but Jev's semantic screening is not completed.
Further reading
Filter configuration guide (Chinese): configuration, operating modes, thresholds, and logging.
Filtering mechanisms (Chinese): three-snippet combination filtering, near-threshold compensation, and inspecting results.
Available Tools
8 toolsbrave_image_searchbrave_image_searchA
Performs an image search using the Brave Search API. Helpful for when you need pictures of people, places, things, graphic design ideas, art inspiration, and more. When relaying results in a markdown environment, it may be helpful to include images in the results (e.g., ).
Inputs: query (required), count, country, safesearch, +2 more. Returns: type, count, items, might_be_offensive
brave_llm_contextbrave_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.
For routine calls, omit the four search budget parameters; the server applies the defaults
shown in their descriptions. Increase a budget only when previous results show that more
source coverage or passage detail is needed. `query` supports site:.
Search rules:
- Unfamiliar subject: first search the subject name plus the core question for an overview,
then verify details as needed; do not search for a given detail directly — check whether
it surfaces naturally in the sources.
- Keep only keywords directly relevant to the current question in `query`; do not pack
context and qualifiers into one query.
- Set `freshness` (pd / pw / pm / py) when recency matters; never hardcode a year in `query`.
- Two consecutive searches with heavily overlapping results mean the direction is exhausted:
change the keyword strategy.
- Search serially; go parallel only when confident of each query.
When relaying results, cite the URL returned with each content item.
Source age, when available, is included with that item; it is not a verified publication date.Inputs: query (required), count, country, goggles, +5 more.
brave_local_searchbrave_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.
Returns detailed information including:
- Business names and addresses
- Ratings and review counts
- Phone numbers and opening hours
Use this when the query implies 'near me', 'in my area', or mentions specific locations (e.g., 'in San Francisco'). This tool automatically falls back to brave_web_search if no local results are found.Inputs: query (required), count, units, offset, +11 more.
brave_news_searchbrave_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.
When to use:
- Finding recent news articles on specific topics
- Getting breaking news updates
- Researching current events or trending stories
- Gathering news sources and headlines for analysis
Returns a JSON list of news-related results with title, url, and description. Some results may contain snippets of text from the article.
When relaying results in markdown-supporting environments, always cite sources with hyperlinks.
Examples:
- "According to [Reuters](https://www.reuters.com/technology/china-bans/), China bans uncertified and recalled power banks on planes".
- "The [New York Times](https://www.nytimes.com/2025/06/27/us/technology/ev-sales.html) reports that Tesla's EV sales have increased by 20%".
- "According to [BBC News](https://www.bbc.com/news/world-europe-65910000), the UK government has announced a new policy to support renewable energy".Inputs: query (required), count, offset, country, +7 more.
brave_place_searchbrave_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.
When to use:
- POIs near coordinates or a named area (e.g. "coffee shops in Paris") -> 'results', each with structured business data (postal address, hours, contact, ratings, photos, categories, timezone).
- Browsing general POIs (omit 'query'; supply 'latitude'+'longitude' or 'location').
- Disambiguating a bare city name (e.g. "springfield") -> 'cities'.
- Resolving a specific address (e.g. "350 5th avenue" with NYC coords) -> 'addresses' (often plus 'streets').
- Looking up a street by name (e.g. "michigan avenue" with Chicago coords) -> 'streets'.
Inputs:
- Anchor the search via 'latitude'+'longitude' or 'location' (or both). With neither, 'query' is required.
- 'addresses' / 'streets' only surface when the query is address-/street-shaped AND geographically anchored.
- 'location' format: US -- '<city> <state> <country>' (e.g. 'san francisco ca united states'); non-US -- '<city> <country>' (e.g. 'tokyo japan'). Capitalization and commas don't matter.
- 'count' caps results (max 50, default 20). 'radius' (meters) biases toward closer results; it does NOT hard-limit the search area.Inputs: count, query, units, accept, +13 more. Returns: type, query, cities, results, +3 more
brave_summarizerbrave_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.
When to use:
- When you need a concise overview of complex topics from multiple sources
- For quick fact-checking or getting key points without reading full articles
- When providing users with summarized information that synthesizes various perspectives
- For research tasks requiring distilled information from web searches
Returns a text summary that consolidates information from the search results. Optional features include inline references to source URLs and additional entity information.
Requirements: Must first perform a web search using brave_web_search with summary=true parameter. Requires a Pro AI subscription to access the summarizer functionality.Inputs: key (required), entity_info, inline_references.
brave_video_searchbrave_video_searchA
Searches for videos using Brave's Video Search API and returns structured video results with metadata.
When to use:
- When you need to find videos related to a specific topic, keyword, or query.
- Useful for discovering video content, getting video metadata, or finding videos from specific creators/publishers.
Returns a JSON list of video-related results with title, url, description, duration, and thumbnail_url.Inputs: query (required), count, offset, country, +5 more.
brave_web_searchbrave_web_searchA
Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata.
When to use:
- General web searches for information, facts, or current topics
- Location-based queries (restaurants, businesses, points of interest)
- News searches for recent events or breaking stories
- Finding videos, discussions, or FAQ content
- Research requiring diverse result types (web pages, images, reviews, etc.)
Returns a JSON list of web results with title, description, and URL.
When the "results_filter" parameter is empty, JSON results may also contain FAQ, Discussions, News, and Video results.Inputs: query (required), count, units, offset, +11 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Web search, Google SERP, page extraction to markdown and cited answers for AI agents.
Web search and page fetch for AI agents. Results come from a shared cache; cached calls cost less.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides web search and content retrieval optimized for AI coding assistants, returning full conversations and structured content from StackOverflow, GitHub Issues, arXiv, and Wikipedia in a single call.405MIT
- AlicenseAqualityDmaintenanceEnables MCP hosts to perform cited web searches and receive source-bearing results with titles, URLs, snippets, and sources for evidence-grounded answers.136 npmMIT
- AlicenseAqualityCmaintenanceProvides AI-driven web search, page fetching, and site mapping with real xAI citations, enabling LLM clients to access up-to-date external information.134MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform live web searches with ranked results and extracted page passages, plus clean markdown extraction of any URL.MIT