| name | exa-search-ops |
| description | Use when Codex needs semantic web search, news reconnaissance, or citation gathering through the Exa MCP server. |
Exa Search Ops
Purpose
Coordinate Exa-based semantic searches for discovery tasks, including link gathering, trend monitoring, and citation harvesting, using the remote configuration defined in servers/exa.
Setup Checklist
- Set
EXA_ENDPOINT,EXA_API_KEY, and (optionally)EXA_DEFAULT_REGION. - Verify the
exaentry exists inmcp.jsonwithmaxResultsmetadata tuned to the task. - Track the current request quota under the Exa dashboard before kicking off large searches.
Workflow
- Frame the question – clarify keywords, negative keywords, date windows, and desired number of results.
- Search – call the
searchtool with structured parameters (topic, start/end date, numResults). Use follow-up expansion judiciously. - Digest – parse the returned snippets, grouping them by theme and ranking by score.
- Cite+Store – log the
title,url, andscorefor each item you surface downstream. Consider persisting curated lists underdocs/exa/.
Notes
- Enforce deduplication by comparing normalized URLs before presenting results.
- Use chronological filters instead of multi calls when researching within a known time range.
- If Exa responds with
rate_limited, wait 10 seconds and retry once before escalating.