← all repositories
exa-labs/exa-mcp-server

An MCP server that gives your AI assistant a search engine

It wires Exa's web, code, and company search into any MCP-compatible client so your agent can look things up without opening a browser.

4.8k stars TypeScript Coding AssistantsAgents
exa-mcp-server
Velocity · 7d
+15
★ / day
Trend
accelerating
star history

What it does

This is a hosted Model Context Protocol server that exposes Exa’s search API as tools for AI assistants. It lets clients like Cursor, VS Code, Claude Code, and others perform web searches, fetch page contents, and run advanced filtered queries through a single HTTP endpoint. You bring an Exa API key; the server handles translating MCP tool calls into search results.

The interesting bit

The project is essentially a well-maintained adapter between Exa’s search backend and the MCP ecosystem, but the real depth lies in its “Agent Skills” — ready-to-drop prompts that teach Claude Code how to do company research or code search without drowning the main context in raw results. It also deprecates a pile of older tools (crawling_exa, people_search_exa, etc.) in favor of a leaner trio, which suggests the authors are actively pruning surface area.

Key highlights

  • Hosted at https://mcp.exa.ai/mcp with support for a dozen+ clients (Cursor, VS Code, Claude Desktop, Zed, Windsurf, etc.)
  • Default toolset is intentionally minimal: web_search_exa, web_fetch_exa, and an opt-in web_search_advanced_exa
  • Includes pre-written Claude Code skills for company research and code context, complete with token-isolation strategies and query-tuning heuristics
  • Can also run locally via the exa-mcp-server npm package

Caveats

  • Several formerly standalone tools (code search, LinkedIn search, deep research) are deprecated and folded into the advanced search tool, so older configs may need updating
  • Category-specific filters (e.g., company searches) have strict restrictions that trigger 400 errors if combined with domain or date filters
  • Requires an Exa API key and sends queries to Exa’s hosted endpoint; it is not a self-contained search engine

Verdict

Worth a look if you want your MCP client to stop hallucinating API syntax and start citing real docs and GitHub repos. Skip it if you already have a local search pipeline or don’t want to manage another API key and external dependency.

Frequently asked

What is exa-labs/exa-mcp-server?
It wires Exa's web, code, and company search into any MCP-compatible client so your agent can look things up without opening a browser.
Is exa-mcp-server open source?
Yes — exa-labs/exa-mcp-server is open source, released under the MIT license.
What language is exa-mcp-server written in?
exa-labs/exa-mcp-server is primarily written in TypeScript.
How popular is exa-mcp-server?
exa-labs/exa-mcp-server has 4.8k stars on GitHub and is currently accelerating.
Where can I find exa-mcp-server?
exa-labs/exa-mcp-server is on GitHub at https://github.com/exa-labs/exa-mcp-server.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.