Exa · MCP server
What leaves our environment when an on-premises agent searches the web with Exa?
The Exa MCP server gives an agent web search and page fetch. The agent, the model and your documents stay on your infrastructure. What leaves is what the agent sends to Exa: the search query and the addresses of the pages it asks for.
What it gives an agent.
Tool by tool.
- 01Search the web
- 02Fetch the content of a page
- web_search_exa
- web_fetch_exa
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 Exa: 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.
Does Exa see our documents?
Not unless the agent puts their content into a search query. Exa receives the query and the addresses of pages the agent asks for.
Who publishes this server?
Exa. It is not Katonic's software. Katonic runs it and governs the calls an agent makes to it.
How is it different from the other search servers?
It offers two tools: search and fetch. Tavily, Brave Search and Firecrawl offer more, such as crawling or news and image search.