Brave Search · MCP server
What leaves our environment when an on-premises agent searches the web with Brave Search?
The Brave Search MCP server gives an agent web, news, image, video and local search through the Brave Search API. The agent, the model and your documents stay on your infrastructure. What leaves is the search query the agent sends to Brave.
What it gives an agent.
Tool by tool.
- 01Search web pages
- 02Search news
- 03Search images and video
- 04Search local places
- 05Get a summary or a context block for a query
- brave_web_search
- brave_news_search
- brave_image_search
- brave_video_search
- brave_local_search
- brave_place_search
- brave_summarizer
- brave_llm_context
Tool names as the public catalog listed them on 15 November 2026
What leaves your environment
What the agent sends.What the agent puts in a call goes to Brave: the search query, and the address of any page it asks for. Your documents, the model and the agent's answer stay on your infrastructure, unless the agent puts their content into a query.
What it needs
An API key. You give it when you connect the server.
How Katonic governs the calls
Tool calls go through the platform's tool gateway. It manages the connection to each MCP server, passes calls from the agent runtime, and applies the allowlists, rate limits and data-classification rules an administrator sets. Tool usage is recorded. A server can be deployed in your cluster or reached as a remote hosted server.
Use case pages that name Brave Search.
Does Brave see our documents?
Not unless the agent puts their content into a search query. Brave receives the query.
Who publishes this server?
Brave. It is not Katonic's software. Katonic runs it and governs the calls an agent makes to it.
Does it read the pages it finds?
It returns search results. To read a full page, an agent uses a server that fetches pages, such as Firecrawl, Tavily or Exa.