- Brand
- Exa
- Category
- Data & Analytics
- Primary Subcategory
- Web Search, Crawling & Extraction for Agents
Integration details
Description
Exa MCP gives you real-time web searches and can extracts content from any URL. It also finds the best code examples and documentation, searches billions of GitHub repos, docs sites, and StackOverflow to give you fresh coding context.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Web Search, Crawling & Extraction for Agents
- Secondary Subcategories
- None listed
- Brand
- Exa
- Access
- Account required
- First tracked
- 2026-04-01
- Tool count
- 2
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Your Claude Discoverability Score is being prepared
Claude can surface a verified Connector when it matches a user’s Prompt.We are preparing Exa’s Discoverability Score and will publish it when the benchmark is ready.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
Get alerts for Exa
Get updates when Exa’s Discoverability Score or category rank changes.
Competing in Claude Web Search, Crawling & Extraction for Agents
View Category2 tools agents can invoke
Exa Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Exa's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Exa alternatives on Claude?
As of 2026-11-02, Exa competes with Anakin, Apify, AWS Web Search, Bastion Helix Agent Lens, BrowsingBee, Cala, Clawifi, Context.dev and 49 more in Claude Web Search, Crawling & Extraction for Agents, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.