Skip to main content
Back to the Exa MCP server

MCP Gateway · Claude Code

Exa icon

Connect Exa to Claude Code

When a library upgrade breaks a build or an API changes under you, the answer is usually somewhere on the web. Exa gives Claude Code web search, full-page reading and code examples from the terminal. Speakeasy's agent hooks check each prompt and tool call before it runs, and Claude Code's OpenTelemetry exporter ties every search to the developer who made it.

Category
AI & search
Tools
8
Authentication
None
Claude Code
CLI

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.

Deploy on MCP Gateway

Set up

Add Exa to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Exa

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Exa from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Exa

Look up an unfamiliar API

Ask Claude Code how a library method is meant to be called, and it pulls code examples and documentation for that exact usage before editing your file.

get_code_context_exa

Read release notes before upgrading

Before bumping a dependency, have Claude Code search for the release notes and read the full page as Markdown, so breaking changes show up before the tests fail.

web_search_exacrawling_exa

Debug an error you don't recognize

Paste a stack trace from the terminal and let Claude Code search code examples and debugging help for it, then apply the fix that fits your codebase.

get_code_context_exaweb_search_exa

Tools

8 tools

Each Exa tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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.

See all 8 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can I stop Claude Code from reading arbitrary URLs with Exa?
Yes. The gateway decides which Exa tools each team can call, so a team can keep web_search_exa and get_code_context_exa without crawling_exa. Agent hooks also send each tool call to Speakeasy, which allows or denies it before Claude Code runs it.
Does each developer need an Exa API key for Claude Code?
No. Each session authenticates through your identity provider, and agents never hold an Exa credential. Access ends when the employee leaves the directory.
How do Claude Code users get Exa?
An admin adds Exa from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Exa tools their access allows.
Are Exa calls from Claude Code logged?
Yes. Exa calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Exa in other clients

AI everywhere.

Control here.