Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 12, 2026·2 min de lectura

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.

MCP Hub
MCP Hub · Community
Listo para agents

Este activo puede ser leído e instalado directamente por agents

TokRepo expone un comando CLI universal, contrato de instalación, metadata JSON, plan según adaptador y contenido raw para que los agents evalúen compatibilidad, riesgo y próximos pasos.

Native · 94/100Política: permitir
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp
Instalación
Single
Confianza
Confianza: Established
Entrada
https://mcp.exa.ai/mcp
Comando CLI universal
npx tokrepo install dc30fe00-f5e3-4bf2-9420-dd003ccdc950
contrato de instalaciónJSON de metadataplan adaptadorcontenido raw
Introducción

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.

🙏

Fuente y agradecimientos

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

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

Apify MCP Server — 8,000+ Web Scrapers for Agents

Apify MCP Server connects agents to Apify Actors via a hosted endpoint (mcp.apify.com) or local run, turning thousands of web scrapers into callable tools.

MCP Configs
MCP Hub

Plane MCP Server — Manage Issues from Agents

Plane MCP Server brings Plane projects and work items into MCP: uvx for local stdio or remote HTTP via mcp.plane.so. Verified 220★; setup ~5–12 minutes.

MCP Configs
MCP Hub

mcp-omnisearch — Unified Search MCP Server

Run mcp-omnisearch as an MCP server to unify Tavily, Brave, Kagi, Exa, GitHub search, and extraction tools behind one interface.

MCP Configs
MCP Hub

WinRemote MCP — Remote Windows Control Server

WinRemote MCP is a Windows MCP server you run on the target machine, exposing desktop automation, process control, and file operations to MCP clients.

MCP Configs
MCP Hub
◈Inicio🔍Buscar👤Yo