Exa MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南
Exa 托管 MCP 服务器,提供 AI 原生网页搜索。支持语义搜索、论文检索、公司调研与页面抓取(需 API Key)。
本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。
🔒 Client-side only — never leaves your browser.
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"exa": {
"url": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}claude mcp add --transport http exa https://mcp.exa.ai/mcp
With credential header:
claude mcp add --transport http exa https://mcp.exa.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"
Or add to .vscode/mcp.json:
{
"servers": {
"exa": {
"type": "http",
"url": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.exa.ai/mcp - Provide your API key / Bearer token when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"exa": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.exa.ai/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"exa": {
"serverUrl": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"exa": {
"url": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.exa] url = "https://mcp.exa.ai/mcp" bearer_token_env_var = "EXA_TOKEN"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"exa": {
"type": "streamableHttp",
"url": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"exa": {
"httpUrl": "https://mcp.exa.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}🧰 Exa MCP 工具与 Schema(11)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| web_search_exa ~32 tok | 🟢 Read | Search the web with Exa neural search. | — |
| get_code_context_exa ~35 tok | 🟢 Read | Get code context for programming queries. | — |
| research_paper_search ~30 tok | 🟢 Read | Search academic papers. | — |
| company_research ~28 tok | 🟢 Read | Research companies. | — |
| crawling ~29 tok | 🟢 Read | Crawl a URL and extract content. | — |
| competitor_finder ~31 tok | 🟢 Read | Find competitors of a company. | — |
| linkedin_search ~33 tok | 🟢 Read | Search LinkedIn profiles and companies. | — |
| wikipedia_search_exa ~29 tok | 🟢 Read | Search Wikipedia. | — |
| github_search ~29 tok | 🟢 Read | Search GitHub repositories. | — |
| deep_researcher_start ~31 tok | 🟠 Write | Start a deep research task. | — |
| deep_researcher_check ~34 tok | 🟢 Read | Check status of a deep research task. | — |
🛡️ 安全评级、质量与上下文 Token 审计
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- Static credential (Bearer token / API key) — protect it in client config
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 与安全
- 认证方式
- API Key
- 动态客户端注册(DCR)
- —
- PKCE S256
- —
- 受保护资源元数据
- https://mcp.exa.ai/.well-known/oauth-protected-resource
📡 官方远程端点与传输协议
远程端点 https://mcp.exa.ai/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。
接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。
🔐 认证与权限机制
认证方式为 API Key。需要在客户端配置中提供 Authorization: Bearer <你的密钥> 请求头,凭据可在 Exa 控制台获取。
🛡️ 上下文开销与安全审计
该服务端当前登记 11 个工具,全部定义合计约 361 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。
🧩 主流客户端快速接入
本站为 Exa MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 web_search_exa、get_code_context_exa、research_paper_search、company_research、crawling 等。
📖 Exa 详解
Exa MCP — Remote MCP Server
Exa's remote MCP wraps its semantic search API for agents: web search tuned for LLM consumption, research-paper search, company research and URL crawling. There is no OAuth flow — you attach an Exa API key, typically via a header or a key-parameterized URL configured in your client.
Official Exa MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.exa.ai/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Exa MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Exa MCP uses API-key authentication rather than OAuth. Get a key from https://docs.exa.ai/reference/exa-mcp, then configure your client to send it — most clients accept an Authorization: Bearer YOUR_API_KEY header, and mcp-remote supports --header arguments.
All 4 cataloged tools are read-only — Exa MCP cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401/403 responses — your credential is missing or rejected. Regenerate the key/token and make sure it is sent as an
Authorization: Bearerheader on every request, including theinitializecall. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - Auth is API-key based, not OAuth — configure a key in your client's header/env settings.
- A free Exa tier exists for low-volume usage.
🚀 如何接入 Exa MCP 远程 MCP
- 获取远程端点 — 复制官方端点 https://mcp.exa.ai/mcp,并先在 Exa 控制台申请 API 凭据。
- 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL 与 Authorization 头(见下方分客户端指南)。
- 授权并验证 — 保存配置后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。
🔌 Exa × 各客户端连接指南
❓ 常见问题
Exa MCP 远程 MCP 服务器是官方提供的吗?
本条目标记为「官方直营」。端点由 Exa 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。
如何在 Claude / Cursor 中连接 Exa MCP?
复制远程端点 https://mcp.exa.ai/mcp:Claude Code 执行 claude mcp add --transport http exa https://mcp.exa.ai/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "exa": { "url": "https://mcp.exa.ai/mcp" } } }。
连接时返回 401 或需要密钥怎么办?
该端点需要 Bearer Token / API Key:在 Exa 控制台申请凭据后,按对应客户端文档将其写入 headers 配置。
本地 stdio MCP 和这个远程 MCP 有什么区别?
本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Exa 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。