exa-search
This Claude Code skill integrates Exa's search API through three specialized tools: web_search_exa for general web searches returning formatted text content, get_code_context_exa for technical documentation and code repository searches, and company_research_exa for company information and news. Use it when you need to retrieve current web information, find code examples and technical documentation, or research company details, configuring parameters like result count, search type, and content length limits as needed.
git clone --depth 1 https://github.com/mxyhi/ok-skills /tmp/exa-search && cp -r /tmp/exa-search/exa-search ~/.claude/skills/exa-searchSKILL.md
# Exa
## Tools and parameters
### web_search_exa
- Purpose: general web search, returns ready-to-use text content
- Parameters:
- `query`: search query (required)
- `numResults`: number of results (default 8)
- `type`: `auto` | `fast` (default `auto`)
- `livecrawl`: `preferred` | `fallback` (default `fallback`)
- `contextMaxCharacters`: max text length (default 10000)
### get_code_context_exa
- Purpose: code/docs/technical search
- Parameters:
- `query`: search query (required)
- `tokensNum`: returned token count (1000-50000, default 5000)
### company_research_exa
- Purpose: company info and news
- Parameters:
- `companyName`: company name (required)
- `numResults`: number of results (default 5)
## Parameter templates (JSON)
### web_search_exa
```
{"query":"...", "numResults":8, "type":"auto", "livecrawl":"preferred", "contextMaxCharacters":10000}
```
### get_code_context_exa
```
{"query":"...", "tokensNum":5000}
```
### company_research_exa
```
{"companyName":"...", "numResults":5}
```
## Invocation examples
```
URL="https://mcp.exa.ai/mcp?tools=web_search_exa,get_code_context_exa,company_research_exa"
npx -y mcporter call --http-url "$URL" --tool web_search_exa --args '{"query":"latest AI safety research"}'
npx -y mcporter call --http-url "$URL" --tool get_code_context_exa --args '{"query":"React useEffect cleanup examples","tokensNum":5000}'
npx -y mcporter call --http-url "$URL" --tool company_research_exa --args '{"companyName":"OpenAI","numResults":5}'
```
## Notes
- Tools and fields reference: `references/exa-tools.md`
- If you need an API key, pass `exaApiKey` as a request parameterBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
Autonomous iteration loop: modify, verify, keep/discard against any metric
Use when working with icons in any project. Provides CLI for searching 200+ icon libraries (Iconify) and retrieving SVGs. Commands: `better-icons search <query>` to find icons, `better-icons get <id>` to get SVG. Also available as MCP server for AI agents.
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
>
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.