Exa + Claude

How to connect Exa to Claude

Connect Exa to Claude through Agent200's MCP server: no separate key, ready-made tools and one API key.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Exa tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects Exa to Claude through Agent200's MCP server. When you finish, Claude can search, read and act in Exa with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Claude with your Agent200 API key. Exa is reached with that key, so there is no separate Exa key to manage.

Connector
Exa
Works with
Claude ยท Agent app, through MCP
Authentication
Your Agent200 API key
Tools
4 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Exa enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

Connect Exa to Claude

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Exa and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Open Connectors in Claude

    On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.

  3. 3

    Step 3: Add a custom connector

    Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.

  4. 4

    Step 4: Send your key as a request header

    Under Authentication choose No sign-in. Open Request headers, pick authorization, enter Bearer followed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.

    Add custom connector
    MCP: Claude custom connector (URL and request header)
    Remote MCP server URL:  https://api.agent200.com/mcp/
    Authentication:         No sign-in
    Request header name:    authorization
    Value:                  Bearer YOUR_AGENT200_API_KEY
  5. 5

    Step 5: Turn it on in a chat

    In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

Test your connection

Run one request to check everything is wired up.

Ask

Find recent papers on retrieval for long documents

What should come back

  • An answer built from Exa results.
  • Behind the scenes, Claude calls an Agent200 tool for Exa, such as exa_search_web.

If Claude says it has no Exa tool, check that Exa is enabled for your project in the dashboard.

Get your API key

Create a key in the Agent200 dashboard. It reaches Exa and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Exa to Claude.

Agent brief
Goal: connect Exa to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/exa/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Exa is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. Check it works with this request: "Find recent papers on retrieval for long documents"
   What should come back:
   - An answer built from Exa results.
   - Behind the scenes, Claude calls an Agent200 tool for Exa, such as `exa_search_web`.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /tools/exa/framework/claude.md

Exa tools Claude can call

  • Search the web

    Read
    exa_search_web

    Find pages that match a query, with filters for domain, date and category.

  • Get page contents

    Read
    exa_get_contents

    Read the text, highlights or summary of chosen pages.

  • Find similar pages

    Read
    exa_find_similar

    Find pages similar to a given URL.

  • Get an answer

    Read
    exa_get_answer

    Answer a question from search results, with citations.

How it works

  1. 01

    You ask Claude

    In your own words, for something in Exa.

  2. 02

    Claude picks a tool

    It sees the Exa tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches Exa with your Agent200 API key, within the endpoints your project allows.

  4. 04

    Claude answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

There is no Request headers section

Request headers are a Claude beta that only some accounts have. Without it, Claude cannot send an API key to a custom connector: use Claude Code, or the Agent200 SDK in your own agent.

Claude cannot reach the server

Check the header value is Bearer, a space, then your key, and that the URL is exactly the Agent200 MCP server address.

A Team or Enterprise member cannot add the connector

Only an Owner adds custom connectors, in Organization settings > Connectors. Members then connect it under Customize > Connectors.

You created a new API key

Claude does not let you edit a connector’s authentication. Remove the Agent200 connector and add it again with the new key.

Claude does not use the Exa tools

Open + > Connectors in that chat and check Agent200 is on, and that no tool is set to Blocked under Customize > Connectors. Naming Exa in the request also helps.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Exa and the tools you need are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Claude's MCP settings, and stop using the old one. Paste the key only into Claude's settings, never into a chat.

Use Exa with another framework

200 OK

Exa, connected to Claude.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)