Web Search (Exa)

Search the web for: $ARGUMENTS

Tool

Use websearchexa for all web search requests.

When to Use

• Current events, news, recent developments
• Fact-checking or verifying claims
• Finding articles, blog posts, documentation
• Any question where the answer may have changed since training data cutoff
• General research and information gathering
• Code examples, API docs, and library usage

Trigger phrases: "search for", "find me", "look up", "what is", "find articles about", "research", "any recent", or any question that may need current information.

How to Search

websearchexa accepts:

• query (string, required) — natural language search query
• numResults (number, optional) — how many results to return

Query Tips

• Write queries as natural language statements, not keywords
• Be specific: "latest React 19 server components changes" beats "react updates"
• Include time context when relevant: "2026 AI regulation proposals"
• For broad topics, run 2-3 queries with different phrasings and merge results

Tuning Results

• Quick lookup → numResults: 3-5
• Standard research → numResults: 5-10 (default)
• Deep dive → numResults: 10-20

Output Format

For every claim or fact, cite the source inline:

1. Lead with the direct answer
2. Support with specific facts, numbers, dates
3. Cite every fact with its source URL
4. End with a Sources section listing all URLs used

Before You Start

Check if Exa MCP is installed by confirming websearchexa is available in your tool list.

If the MCP Server Is Not Connected

You (the AI) must:

1. Stop immediately — do NOT search the web yourself, do NOT use websearch, and do NOT try to answer the query from your own knowledge.
2. Inform the user that Exa MCP is not connected.

Request the user to:

1. Run the /exa-setup command in Cursor to add the Exa MCP server.
2. Go to Cursor Settings → Tools & MCP and make sure Exa is toggled on (green).
3. Retry their search after completing the above steps.