# Exa MCP Server — Remote Search Tools for Agents

> Exa MCP Server connects clients to Exa’s hosted web/code search tools via a remote MCP URL, with simple config for Cursor, VS Code, Claude Code, and Codex.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

1. Use the hosted MCP endpoint:
   ```
   https://mcp.exa.ai/mcp
   ```
2. Add to Claude Code:
   ```bash
   claude mcp add --transport http exa https://mcp.exa.ai/mcp
   ```
3. Add to Codex:
   ```bash
   codex mcp add exa --url https://mcp.exa.ai/mcp
   ```

## Intro

Exa MCP Server connects clients to Exa’s hosted web/code search tools via a remote MCP URL, with simple config for Cursor, VS Code, Claude Code, and Codex.

- **Best for:** agent builders who want high-quality search tools without running local infra
- **Works with:** MCP clients with HTTP transport (Cursor/VS Code/Claude Code/Codex), Exa API key
- **Setup time:** 5–15 minutes

## Practical Notes

- Data point: it’s a hosted remote MCP URL (no local server required).
- Quant: budget 1–2 minutes to validate auth and a first tool call.

## Pattern: keep search as a dedicated tool

In agent setups, keep search separate from browsing:
- search finds candidates (URLs/snippets),
- browsing fetches and verifies content.

This reduces hallucinations because the agent can cite the tool result, then confirm with a second step.

## Operational tips

- Prefer HTTP transport for multi-user clients.
- Treat the API key like any other secret (CI secret store, not in git).

### FAQ

**Q: Do I have to run this server myself?**
A: No. The repo documents a hosted endpoint you can connect to directly.

**Q: Which transport should I use?**
A: Use HTTP transport when your client supports it.

**Q: What if tools fail?**
A: Verify the MCP URL is reachable and the API key is configured correctly in your client.

## Source & Thanks

> Source: https://github.com/exa-labs/exa-mcp-server
> License: MIT
> GitHub stars: 4,413 · forks: 331

---

<!-- ZH -->

## 快速使用

1. 使用官方托管的 MCP 地址：
   ```
   https://mcp.exa.ai/mcp
   ```
2. 添加到 Claude Code：
   ```bash
   claude mcp add --transport http exa https://mcp.exa.ai/mcp
   ```
3. 添加到 Codex：
   ```bash
   codex mcp add exa --url https://mcp.exa.ai/mcp
   ```

## 简介

Exa MCP Server 通过远程 MCP URL 把 Exa 的网页/代码搜索能力接入客户端；只需配置一个 URL，即可在 Cursor、VS Code、Claude Code、Codex 等客户端使用。

- **适合谁：** 想直接用高质量搜索工具、但不想自建服务的 agent 开发者
- **可搭配：** 支持 HTTP transport 的 MCP 客户端（Cursor/VS Code/Claude Code/Codex）与 Exa API key
- **准备时间：** 5–15 分钟

## 实战建议

- 数据点：它是托管的远程 MCP URL，不需要本地起服务。
- 量化建议：预留 1–2 分钟验证鉴权与第一次工具调用。

## 常用打法：把“搜索”当成独立工具

在 agent 工作流里，建议把搜索与浏览分开：
- 搜索负责找候选（URL/片段），
- 浏览负责拉取与核验。

这样能降低幻觉：先引用工具返回，再做二次确认。

## 运维建议

- 多人/多会话场景优先用 HTTP transport。
- API key 用密钥管理，不要提交到仓库。

### FAQ

**需要自己部署吗？**
答：不需要。仓库提供了可直接连接的托管端点。

**该用哪种 transport？**
答：客户端支持的话优先用 HTTP transport。

**工具调用失败怎么办？**
答：先检查 MCP URL 可达性，再检查 API key 配置是否正确。

## 来源与感谢

> Source: https://github.com/exa-labs/exa-mcp-server
> License: MIT
> GitHub stars: 4,413 · forks: 331


---
Source: https://tokrepo.com/en/workflows/exa-mcp-server-remote-search-tools-for-agents
Author: MCP Hub