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

Staging seguro para este activo

Este activo primero queda en staging. El prompt copiado pide inspeccionar los archivos staged antes de activar scripts, config MCP o config global.

Stage only · 17/100Política: staging
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp Config
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando de staging seguro
npx -y tokrepo@latest install dc30fe00-f5e3-4bf2-9420-dd003ccdc950 --target codex

Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.

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

GitMCP — Remote MCP Server for Any GitHub Repo

Free remote MCP server that gives AI agents context from any GitHub project. Eliminates code hallucinations by providing real README, docs, and code. Zero setup. 7.8K+ stars.

MCP Configs
MCP Hub

WhatsApp MCP Server — Chat with WhatsApp via AI Agents

MCP server connecting Claude and AI agents to your personal WhatsApp. Search contacts, read messages, send replies and media via natural language.

MCP Configs
MCP Hub

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

google-tag-manager-mcp-server — GTM MCP Remote Connector

Connect Google Tag Manager to MCP clients via an OAuth-backed remote server using mcp-remote + npx. Verified 152★; pushed 2026-05-14.

MCP Configs
MCP Hub
◈Inicio🔍Buscar👤Yo