Mcp Exa
Let your agent run Exa neural web search from the IDE instead of stale training data or manual tab hopping.
Overview
io.github.daedalus/mcp-exa is an MCP server for the Idea phase that exposes Exa web search tools to your agent over stdio.
What is this MCP server?
- Stdio MCP bridge to the Exa web search API
- PyPI package mcp-exa v0.1.1
- Agent-callable search without leaving Claude Code or Cursor
- Suited to competitor URLs, technical references, and launch intel
- GitHub-hosted daedalus/mcp-exa with MCP schema 2025-12-11
- Server version 0.1.1
- Transport: stdio
- PyPI identifier: mcp-exa
Who is it for?
Solo founders doing competitor and documentation research inside an MCP-enabled coding agent with an Exa API key.
Skip if: Builders who only need on-repo context or who cannot use paid third-party search APIs.
What do I get? / Deliverables
Your agent issues Exa search calls through MCP and grounds answers in retrievable web sources while you ideate.
- Exa search tools available to the agent via MCP
- Repeatable web-grounded research workflow from the IDE
Recommended MCP Servers
Journey fit
Web search MCPs belong on Idea first because builders use them to validate markets, find docs, and gather sources before committing to a stack. Research is the canonical shelf for Exa-powered discovery—competitive scans, API docs, and trend checks during early exploration.
How it compares
Exa search API MCP bridge, not a full browser automation or scraping suite.
Common Questions / FAQ
Who is io.github.daedalus/mcp-exa for?
Indie builders and agent users who want programmatic Exa web search during idea and validation research.
When should I use io.github.daedalus/mcp-exa?
Use it when you need fresh URLs, competitor pages, or technical references while scoping a product in Claude Code or Cursor.
How do I add io.github.daedalus/mcp-exa to my agent?
Obtain an Exa API key, install mcp-exa from PyPI, configure stdio MCP with your key per Exa’s env requirements, and reload the client.