MCP Gateway · Claude
Connect Exa to Claude
Exa gives Claude live web search and page reading, so answers about a market, a competitor or a news story come from current pages. An Owner adds the gateway once as a custom connector and each person connects it from Customize > Connectors. People only see the servers their role can reach, and nobody handles an Exa credential.
- Category
- AI & search
- Tools
- 8
- Authentication
- None
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Exa MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Exa call inspected and logged.
Set up
Add Exa to Claude in 4 steps
- 01
Add Exa from the catalog
An admin finds Exa in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Exa
Give teams the
mcp:connectscope on the Exa server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Exa to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Exa from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Exa's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Exa
Brief yourself before a customer call
Ask Claude to search for a prospect's recent announcements, funding news and product launches, then turn what it finds into a short brief with links.
Summarize a long report from a link
Paste the URL of an industry report or policy page and Claude reads the full text as Markdown, then pulls out the points that matter for your team.
Track coverage of a topic
Ask Claude to gather this week's coverage of a regulation or a competitor, read the most relevant articles in full and list what changed.
Tools
8 tools
Each Exa tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
web_search_exa
Search the web for any topic and get clean, ready-to-use content.
company_research_exa
[Deprecated: Use web_search_advanced_exa instead] Research any company to get business information, news, and insights.
crawling_exa
Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL.
people_search_exa
[Deprecated: Use web_search_advanced_exa instead] Find people and their professional profiles.
linkedin_search_exa
⚠️ DEPRECATED: This tool is deprecated. Please use 'people_search_exa' instead. This tool will be removed in a future version. For now, it searches for people on LinkedIn using Exa AI - finds professional profiles and people.
deep_researcher_start
[Deprecated] Start an AI research agent that searches, reads, and writes a detailed report. Takes 15 seconds to 2 minutes.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Exa call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Exa tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Exa can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can risky prompts be stopped before Claude answers?
Do Speakeasy budgets apply to Exa use in Claude?
How do Claude users get Exa?
Are Exa calls from Claude logged?
Connect more