# Exa MCP Server [![Install in Cursor](https://img.shields.io/badge/Install_in-Cursor-000000?style=flat-square&logoColor=white)](https://cursor.com/en/install-mcp?name=exa&config=eyJuYW1lIjoiZXhhIiwidHlwZSI6Imh0dHAiLCJ1cmwiOiJodHRwczovL21jcC5leGEuYWkvbWNwIn0=) [![Install in VS Code](https://img.shields.io/badge/Install_in-VS_Code-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect/mcp/install?name=exa&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.exa.ai%2Fmcp%22%7D) [![npm version](https://badge.fury.io/js/exa-mcp-server.svg)](https://www.npmjs.com/package/exa-mcp-server) Connect AI assistants to Exa's search capabilities: web search, code search, and company research. **[Full Documentation](https://docs.exa.ai/reference/exa-mcp)** | **[npm Package](https://www.npmjs.com/package/exa-mcp-server)** | **[Get Your Exa API Key](https://dashboard.exa.ai/api-keys)** ## Installation Connect to Exa's hosted MCP server: ``` https://mcp.exa.ai/mcp ``` [Get your API key](https://dashboard.exa.ai/api-keys)

Cursor

Add to `~/.cursor/mcp.json`: ```json { "mcpServers": { "exa": { "url": "https://mcp.exa.ai/mcp" } } } ```

VS Code

Add to `.vscode/mcp.json`: ```json { "servers": { "exa": { "type": "http", "url": "https://mcp.exa.ai/mcp" } } } ```

Claude Code

```bash claude mcp add --transport http exa https://mcp.exa.ai/mcp ```

Claude Desktop

Add to your config file: - **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "exa": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.exa.ai/mcp"] } } } ```

Codex

```bash codex mcp add exa --url https://mcp.exa.ai/mcp ```

OpenCode

Add to your `opencode.json`: ```json { "mcp": { "exa": { "type": "remote", "url": "https://mcp.exa.ai/mcp", "enabled": true } } } ```

Antigravity

Open the MCP Store panel (from the "..." dropdown in the side panel), then add a custom server with: ``` https://mcp.exa.ai/mcp ```

Windsurf

Add to `~/.codeium/windsurf/mcp_config.json`: ```json { "mcpServers": { "exa": { "serverUrl": "https://mcp.exa.ai/mcp" } } } ```

Zed

Add to your Zed settings: ```json { "context_servers": { "exa": { "url": "https://mcp.exa.ai/mcp" } } } ```

Gemini CLI

Add to `~/.gemini/settings.json`: ```json { "mcpServers": { "exa": { "httpUrl": "https://mcp.exa.ai/mcp" } } } ```

v0 by Vercel

In v0, select **Prompt Tools** > **Add MCP** and enter: ``` https://mcp.exa.ai/mcp ```

Warp

Go to **Settings** > **MCP Servers** > **Add MCP Server** and add: ```json { "exa": { "url": "https://mcp.exa.ai/mcp" } } ```

Kiro

Add to `~/.kiro/settings/mcp.json`: ```json { "mcpServers": { "exa": { "url": "https://mcp.exa.ai/mcp" } } } ```

Roo Code

Add to your Roo Code MCP config: ```json { "mcpServers": { "exa": { "type": "streamable-http", "url": "https://mcp.exa.ai/mcp" } } } ```

Other Clients

For clients that support remote MCP: ```json { "mcpServers": { "exa": { "url": "https://mcp.exa.ai/mcp" } } } ``` For clients that need mcp-remote: ```json { "mcpServers": { "exa": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.exa.ai/mcp"] } } } ```

Via npm Package

Use the npm package with your API key. [Get your API key](https://dashboard.exa.ai/api-keys). ```json { "mcpServers": { "exa": { "command": "npx", "args": ["-y", "exa-mcp-server"], "env": { "EXA_API_KEY": "your_api_key" } } } } ```

## Available Tools **Enabled by Default:** | Tool | Description | | ---- | ----------- | | `web_search_exa` | Search the web for any topic and get clean, ready-to-use content | | `get_code_context_exa` | Find code examples, documentation, and programming solutions from GitHub, Stack Overflow, and docs | **Off by Default:** | Tool | Description | | ---- | ----------- | | `web_search_advanced_exa` | Advanced web search with full control over filters, domains, dates, and content options | | `crawling_exa` | Get the full content of a specific webpage from a known URL | Enable additional tools with the `tools` parameter: ``` https://mcp.exa.ai/mcp?exaApiKey=YOUR_KEY&tools=web_search_exa,web_search_advanced_exa,get_code_context_exa,crawling_exa ``` ## Agent Skills (Claude Skills) Ready-to-use skills for Claude Code. Each skill teaches Claude how to use Exa search for a specific task. Copy the content inside a dropdown and paste it into Claude Code — it handles the rest.

Company Research

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: company-research description: Company research using Exa search. Finds company info, competitors, news, tweets, financials, LinkedIn profiles, builds company lists. Use when researching companies, doing competitor analysis, market research, or building company lists. context: fork --- # Company Research ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa`. Do NOT use `web_search_exa` or any other Exa tools. ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent runs Exa search internally - Agent processes results using LLM intelligence - Agent returns only distilled output (compact JSON or brief markdown) - Main context stays clean regardless of search volume ## Dynamic Tuning No hardcoded numResults. Tune to user intent: - User says "a few" → 10-20 - User says "comprehensive" → 50-100 - User specifies number → match it - Ambiguous? Ask: "How many companies would you like?" ## Query Variation Exa returns different results for different phrasings. For coverage: - Generate 2-3 query variations - Run in parallel - Merge and deduplicate ## Categories Use appropriate Exa `category` depending on what you need: - `company` → homepages, rich metadata (headcount, location, funding, revenue) - `news` → press coverage, announcements - `tweet` → social presence, public commentary - `people` → LinkedIn profiles (public data) - No category (`type: "auto"`) → general web results, deep dives, broader context Start with `category: "company"` for discovery, then use other categories or no category with `livecrawl: "fallback"` for deeper research. ### Category-Specific Filter Restrictions When using `category: "company"`, these parameters cause 400 errors: - `includeDomains` / `excludeDomains` - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` When searching without a category (or with `news`), domain and date filters work fine. **Universal restriction:** `includeText` and `excludeText` only support **single-item arrays**. Multi-item arrays cause 400 errors across all categories. ## LinkedIn Public LinkedIn via Exa: `category: "people"`, no other filters. Auth-required LinkedIn → use Claude in Chrome browser fallback. ## Browser Fallback Auto-fallback to Claude in Chrome when: - Exa returns insufficient results - Content is auth-gated - Dynamic pages need JavaScript ## Examples ### Discovery: find companies in a space ``` web_search_advanced_exa { "query": "AI infrastructure startups San Francisco", "category": "company", "numResults": 20, "type": "auto" } ``` ### Deep dive: research a specific company ``` web_search_advanced_exa { "query": "Anthropic funding rounds valuation 2024", "type": "deep", "livecrawl": "fallback", "numResults": 10, "includeDomains": ["techcrunch.com", "crunchbase.com", "bloomberg.com"] } ``` ### News coverage ``` web_search_advanced_exa { "query": "Anthropic AI safety", "category": "news", "numResults": 15, "startPublishedDate": "2024-01-01" } ``` ### LinkedIn profiles ``` web_search_advanced_exa { "query": "VP Engineering AI infrastructure", "category": "people", "numResults": 20 } ``` ## Output Format Return: 1) Results (structured list; one company per row) 2) Sources (URLs; 1-line relevance each) 3) Notes (uncertainty/conflicts) Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

Code Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=get_code_context_exa" Step 2: Add this Claude skill --- name: get-code-context-exa description: Code context using Exa. Finds real snippets and docs from GitHub, StackOverflow, and technical docs. Use when searching for code examples, API syntax, library documentation, or debugging help. context: fork --- # Code Context (Exa) ## Tool Restriction (Critical) ONLY use `get_code_context_exa`. Do NOT use other Exa tools. ## Token Isolation (Critical) Never run Exa in main context. Always spawn Task agents: - Agent calls `get_code_context_exa` - Agent extracts the minimum viable snippet(s) + constraints - Agent deduplicates near-identical results (mirrors, forks, repeated StackOverflow answers) before presenting - Agent returns copyable snippets + brief explanation - Main context stays clean regardless of search volume ## When to Use Use this tool for ANY programming-related request: - API usage and syntax - SDK/library examples - config and setup patterns - framework "how to" questions - debugging when you need authoritative snippets ## Inputs (Supported) `get_code_context_exa` supports: - `query` (string, required) - `tokensNum` (number, optional; default ~5000; typical range 1000–50000) ## Query Writing Patterns (High Signal) To reduce irrelevant results and cross-language noise: - Always include the **programming language** in the query. - Example: use **"Go generics"** instead of just **"generics"**. - When applicable, also include **framework + version** (e.g., "Next.js 14", "React 19", "Python 3.12"). - Include exact identifiers (function/class names, config keys, error messages) when you have them. ## Dynamic Tuning Token strategy: - Focused snippet needed → tokensNum 1000–3000 - Most tasks → tokensNum 5000 - Complex integration → tokensNum 10000–20000 - Only go larger when necessary (avoid dumping large context) ## Output Format (Recommended) Return: 1) Best minimal working snippet(s) (keep it copy/paste friendly) 2) Notes on version / constraints / gotchas 3) Sources (URLs if present in returned context) Before presenting: - Deduplicate similar results and keep only the best representative snippet per approach. ## MCP Configuration ```json { "servers": { "exa": { "type": "http", "url": "https://mcp.exa.ai/mcp?tools=get_code_context_exa" } } } ``` Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

People Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: people-research description: People research using Exa search. Finds LinkedIn profiles, professional backgrounds, experts, team members, and public bios across the web. Use when searching for people, finding experts, or looking up professional profiles. context: fork --- # People Research ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa`. Do NOT use `web_search_exa` or any other Exa tools. ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent runs Exa search internally - Agent processes results using LLM intelligence - Agent returns only distilled output (compact JSON or brief markdown) - Main context stays clean regardless of search volume ## Dynamic Tuning No hardcoded numResults. Tune to user intent: - User says "a few" → 10-20 - User says "comprehensive" → 50-100 - User specifies number → match it - Ambiguous? Ask: "How many profiles would you like?" ## Query Variation Exa returns different results for different phrasings. For coverage: - Generate 2-3 query variations - Run in parallel - Merge and deduplicate ## Categories Use appropriate Exa `category` depending on what you need: - `people` → LinkedIn profiles, public bios (primary for discovery) - `personal site` → personal blogs, portfolio sites, about pages - `news` → press mentions, interviews, speaker bios - No category (`type: "auto"`) → general web results, broader context Start with `category: "people"` for profile discovery, then use other categories or no category with `livecrawl: "fallback"` for deeper research on specific individuals. ### Category-Specific Filter Restrictions When using `category: "people"`, these parameters cause errors: - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` - `includeText` / `excludeText` - `excludeDomains` - `includeDomains` — **LinkedIn domains only** (e.g., "linkedin.com") When searching without a category, all parameters are available (but `includeText`/`excludeText` still only support single-item arrays). ## LinkedIn Public LinkedIn via Exa: `category: "people"`, no other filters. Auth-required LinkedIn → use Claude in Chrome browser fallback. ## Browser Fallback Auto-fallback to Claude in Chrome when: - Exa returns insufficient results - Content is auth-gated - Dynamic pages need JavaScript ## Examples ### Discovery: find people by role ``` web_search_advanced_exa { "query": "VP Engineering AI infrastructure", "category": "people", "numResults": 20, "type": "auto" } ``` ### With query variations ``` web_search_advanced_exa { "query": "machine learning engineer San Francisco", "category": "people", "additionalQueries": ["ML engineer SF", "AI engineer Bay Area"], "numResults": 25, "type": "deep" } ``` ### Deep dive: research a specific person ``` web_search_advanced_exa { "query": "Dario Amodei Anthropic CEO background", "type": "auto", "livecrawl": "fallback", "numResults": 15 } ``` ### News mentions ``` web_search_advanced_exa { "query": "Dario Amodei interview", "category": "news", "numResults": 10, "startPublishedDate": "2024-01-01" } ``` ## Output Format Return: 1) Results (name, title, company, location if available) 2) Sources (Profile URLs) 3) Notes (profile completeness, verification status) Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

Financial Report Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: web-search-advanced-financial-report description: Search for financial reports using Exa advanced search. Near-full filter support for finding SEC filings, earnings reports, and financial documents. Use when searching for 10-K filings, quarterly earnings, or annual reports. context: fork --- # Web Search Advanced - Financial Report Category ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa` with `category: "financial report"`. Do NOT use other categories or tools. ## Filter Restrictions (Critical) The `financial report` category has one known restriction: - `excludeText` - NOT SUPPORTED (causes 400 error) ## Supported Parameters ### Core - `query` (required) - `numResults` - `type` ("auto", "fast", "deep", "neural") ### Domain filtering - `includeDomains` (e.g., ["sec.gov", "investor.apple.com"]) - `excludeDomains` ### Date filtering (ISO 8601) - Very useful for financial reports! - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` ### Text filtering - `includeText` (must contain ALL) - **single-item arrays only**; multi-item causes 400 - ~~`excludeText`~~ - NOT SUPPORTED ### Content extraction - `textMaxCharacters` / `contextMaxCharacters` - `enableSummary` / `summaryQuery` - `enableHighlights` / `highlightsNumSentences` / `highlightsPerUrl` / `highlightsQuery` ### Additional - `additionalQueries` - `livecrawl` / `livecrawlTimeout` - `subpages` / `subpageTarget` ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent calls `web_search_advanced_exa` with `category: "financial report"` - Agent merges + deduplicates results before presenting - Agent returns distilled output (brief markdown or compact JSON) - Main context stays clean regardless of search volume ## When to Use Use this category when you need: - SEC filings (10-K, 10-Q, 8-K, S-1) - Quarterly earnings reports - Annual reports - Investor presentations - Financial statements ## Examples SEC filings for a company: ``` web_search_advanced_exa { "query": "Anthropic SEC filing S-1", "category": "financial report", "numResults": 10, "type": "auto" } ``` Recent earnings reports: ``` web_search_advanced_exa { "query": "Q4 2025 earnings report technology", "category": "financial report", "startPublishedDate": "2025-10-01", "numResults": 20, "type": "auto" } ``` Specific filing type: ``` web_search_advanced_exa { "query": "10-K annual report AI companies", "category": "financial report", "includeDomains": ["sec.gov"], "startPublishedDate": "2025-01-01", "numResults": 15, "type": "deep" } ``` Risk factors analysis: ``` web_search_advanced_exa { "query": "risk factors cybersecurity", "category": "financial report", "includeText": ["cybersecurity"], "numResults": 10, "enableHighlights": true, "highlightsQuery": "What are the main cybersecurity risks?" } ``` ## Output Format Return: 1) Results (company name, filing type, date, key figures/highlights) 2) Sources (Filing URLs) 3) Notes (reporting period, any restatements, auditor notes) Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

Research Paper Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: web-search-advanced-research-paper description: Search for research papers and academic content using Exa advanced search. Full filter support including date ranges and text filtering. Use when searching for academic papers, arXiv preprints, or scientific research. context: fork --- # Web Search Advanced - Research Paper Category ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa` with `category: "research paper"`. Do NOT use other categories or tools. ## Full Filter Support The `research paper` category supports ALL available parameters: ### Core - `query` (required) - `numResults` - `type` ("auto", "fast", "deep", "neural") ### Domain filtering - `includeDomains` (e.g., ["arxiv.org", "openreview.net"]) - `excludeDomains` ### Date filtering (ISO 8601) - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` ### Text filtering - `includeText` (must contain ALL) - `excludeText` (exclude if ANY match) **Array size restriction:** `includeText` and `excludeText` only support **single-item arrays**. Multi-item arrays (2+ items) cause 400 errors. To match multiple terms, put them in the `query` string or run separate searches. ### Content extraction - `textMaxCharacters` / `contextMaxCharacters` - `enableSummary` / `summaryQuery` - `enableHighlights` / `highlightsNumSentences` / `highlightsPerUrl` / `highlightsQuery` ### Additional - `userLocation` - `moderation` - `additionalQueries` - `livecrawl` / `livecrawlTimeout` - `subpages` / `subpageTarget` ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent calls `web_search_advanced_exa` with `category: "research paper"` - Agent merges + deduplicates results before presenting - Agent returns distilled output (brief markdown or compact JSON) - Main context stays clean regardless of search volume ## When to Use Use this category when you need: - Academic papers from arXiv, OpenReview, PubMed, etc. - Scientific research on specific topics - Literature reviews with date filtering - Papers containing specific methodologies or terms ## Examples Recent papers on a topic: ``` web_search_advanced_exa { "query": "transformer attention mechanisms efficiency", "category": "research paper", "startPublishedDate": "2024-01-01", "numResults": 15, "type": "auto" } ``` Papers from specific venues: ``` web_search_advanced_exa { "query": "large language model agents", "category": "research paper", "includeDomains": ["arxiv.org", "openreview.net"], "includeText": ["LLM"], "numResults": 20, "type": "deep" } ``` ## Output Format Return: 1) Results (structured list with title, authors, date, abstract summary) 2) Sources (URLs with publication venue) 3) Notes (methodology differences, conflicting findings) Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

Personal Site Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: web-search-advanced-personal-site description: Search personal websites and blogs using Exa advanced search. Full filter support for finding individual perspectives, portfolios, and personal blogs. Use when searching for personal sites, blog posts, or portfolio websites. context: fork --- # Web Search Advanced - Personal Site Category ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa` with `category: "personal site"`. Do NOT use other categories or tools. ## Full Filter Support The `personal site` category supports ALL available parameters: ### Core - `query` (required) - `numResults` - `type` ("auto", "fast", "deep", "neural") ### Domain filtering - `includeDomains` - `excludeDomains` (e.g., exclude Medium if you want independent blogs) ### Date filtering (ISO 8601) - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` ### Text filtering - `includeText` (must contain ALL) - `excludeText` (exclude if ANY match) **Array size restriction:** `includeText` and `excludeText` only support **single-item arrays**. Multi-item arrays (2+ items) cause 400 errors. To match multiple terms, put them in the `query` string or run separate searches. ### Content extraction - `textMaxCharacters` / `contextMaxCharacters` - `enableSummary` / `summaryQuery` - `enableHighlights` / `highlightsNumSentences` / `highlightsPerUrl` / `highlightsQuery` ### Additional - `additionalQueries` - `livecrawl` / `livecrawlTimeout` - `subpages` / `subpageTarget` - useful for exploring portfolio sites ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent calls `web_search_advanced_exa` with `category: "personal site"` - Agent merges + deduplicates results before presenting - Agent returns distilled output (brief markdown or compact JSON) - Main context stays clean regardless of search volume ## When to Use Use this category when you need: - Individual expert opinions and experiences - Personal blog posts on technical topics - Portfolio websites - Independent analysis (not corporate content) - Deep dives and tutorials from practitioners ## Examples Technical blog posts: ``` web_search_advanced_exa { "query": "building production LLM applications lessons learned", "category": "personal site", "numResults": 15, "type": "deep", "enableSummary": true } ``` Recent posts on a topic: ``` web_search_advanced_exa { "query": "Rust async runtime comparison", "category": "personal site", "startPublishedDate": "2025-01-01", "numResults": 10, "type": "auto" } ``` Exclude aggregators: ``` web_search_advanced_exa { "query": "startup founder lessons", "category": "personal site", "excludeDomains": ["medium.com", "substack.com"], "numResults": 15, "type": "auto" } ``` ## Output Format Return: 1) Results (title, author/site name, date, key insights) 2) Sources (URLs) 3) Notes (author expertise, potential biases, depth of coverage) Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

X/Twitter Search

Copy the content below and paste it into Claude Code. It will set up the MCP connection and skill for you. ```` Step 1: Install or update Exa MCP If Exa MCP already exists in your MCP configuration, either uninstall it first and install the new one, or update your existing MCP config with this endpoint. Run this command in your terminal: claude mcp add --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_advanced_exa" Step 2: Add this Claude skill --- name: web-search-advanced-tweet description: Search tweets and Twitter/X content using Exa advanced search. Limited filter support - text and domain filters are NOT supported. Use when searching for tweets, Twitter/X discussions, or social media sentiment. context: fork --- # Web Search Advanced - Tweet Category ## Tool Restriction (Critical) ONLY use `web_search_advanced_exa` with `category: "tweet"`. Do NOT use other categories or tools. ## Filter Restrictions (Critical) The `tweet` category has **LIMITED filter support**. The following parameters are **NOT supported** and will cause 400 errors: - `includeText` - NOT SUPPORTED - `excludeText` - NOT SUPPORTED - `includeDomains` - NOT SUPPORTED - `excludeDomains` - NOT SUPPORTED - `moderation` - NOT SUPPORTED (causes 500 server error) ## Supported Parameters ### Core - `query` (required) - `numResults` - `type` ("auto", "fast", "deep", "neural") ### Date filtering (ISO 8601) - Use these instead of text filters! - `startPublishedDate` / `endPublishedDate` - `startCrawlDate` / `endCrawlDate` ### Content extraction - `textMaxCharacters` / `contextMaxCharacters` - `enableHighlights` / `highlightsNumSentences` / `highlightsPerUrl` / `highlightsQuery` - `enableSummary` / `summaryQuery` ### Additional - `additionalQueries` - useful for hashtag variations - `livecrawl` / `livecrawlTimeout` - use "preferred" for recent tweets ## Token Isolation (Critical) Never run Exa searches in main context. Always spawn Task agents: - Agent calls `web_search_advanced_exa` with `category: "tweet"` - Agent merges + deduplicates results before presenting - Agent returns distilled output (brief markdown or compact JSON) - Main context stays clean regardless of search volume ## When to Use Use this category when you need: - Social discussions on a topic - Product announcements from company accounts - Developer opinions and experiences - Trending topics and community sentiment - Expert takes and threads ## Examples Recent tweets on a topic: ``` web_search_advanced_exa { "query": "Claude Code MCP experience", "category": "tweet", "startPublishedDate": "2025-01-01", "numResults": 20, "type": "auto", "livecrawl": "preferred" } ``` Search with specific keywords (put keywords in query, not includeText): ``` web_search_advanced_exa { "query": "launching announcing new open source release", "category": "tweet", "startPublishedDate": "2025-12-01", "numResults": 15, "type": "auto" } ``` Developer sentiment (use specific query terms instead of excludeText): ``` web_search_advanced_exa { "query": "developer experience DX frustrating painful", "category": "tweet", "numResults": 20, "type": "deep", "livecrawl": "preferred" } ``` ## Output Format Return: 1) Results (tweet content, author handle, date, engagement if visible) 2) Sources (Tweet URLs) 3) Notes (sentiment summary, notable accounts, threads vs single tweets) Important: Be aware that tweet content can be informal, sarcastic, or context-dependent. Step 3: Ask User to Restart Claude Code You should ask the user to restart Claude Code to have the config changes take effect. ````

## Links - [Documentation](https://docs.exa.ai/reference/exa-mcp) - [npm Package](https://www.npmjs.com/package/exa-mcp-server) - [Get Your Exa API Key](https://dashboard.exa.ai/api-keys)
Built with ❤️ by Exa

Exa Mcp Server

Install

Exa Mcp Server

Install