Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Exa MCP integration for advanced search, research, and crawling.
Exa MCP integration for advanced search, research, and crawling.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill provides access to Exa's powerful search and research capabilities through the Exa MCP server.
exa-search <tool> '{"json":"args"}' - Generic wrapper for any Exa MCP tool
exa-web-search '{"query":"...", "count":10, "freshness":"pw", ...}' - Web search with optional filters
All tools from the Exa MCP server are available: ToolDescriptionweb_search_exaSearch the web for any topic, get clean contentweb_search_advanced_exaAdvanced search with filters (domains, dates, content options)get_code_context_exaFind code examples, documentation, programming solutionscrawling_exaGet full content of a specific webpage from a known URLcompany_research_exaResearch any company for business information and newspeople_search_exaFind people and their professional profilesdeep_researcher_startStart an AI research agent that writes detailed reportsdeep_researcher_checkCheck status and get results from deep research task
Get your Exa API key from https://dashboard.exa.ai/api-keys Set the environment variable: export EXA_API_KEY="your_exa_api_key_here" Or add to your shell profile (~/.bashrc or ~/.zshrc): export EXA_API_KEY="your_exa_api_key_here" Or create a .env file in your workspace: echo "EXA_API_KEY=your_exa_api_key_here" > ~/.openclaw/workspace/.env source ~/.openclaw/workspace/.env Restart OpenClaw to load the skill: openclaw gateway restart
exa-web-search '{"query":"Step-3.5 Flash benchmarks"}'
exa-search web_search_advanced_exa '{ "query": "OpenClaw AI", "count": 10, "freshness": "pw", "includeDomains": ["github.com", "docs.openclaw.ai"] }'
exa-search get_code_context_exa '{ "query": "OpenClaw agent implementation", "count": 5 }'
exa-search crawling_exa '{ "url": "https://docs.openclaw.ai/", "maxPages": 10 }'
exa-search company_research_exa '{ "company": "OpenClaw", "includeNews": true, "newsDays": 30 }'
exa-search people_search_exa '{ "query": "Phil openclaw creator", "count": 10 }'
# Start research TASK_ID=$(exa-search deep_researcher_start '{ "query": "Current state of AI agents in 2026", "maxSources": 20 }' | jq -r '.taskId') # Check status (poll until complete) while true; do exa-search deep_researcher_check '{"taskId":"'"$TASK_ID"'"}' sleep 5 done
All tools return JSON with the Exa MCP response structure. The actual content is in the result field, which varies by tool but typically includes: content: Array of result items with title, url, text (snippet) Sometimes additional metadata like cost, duration, sources Example web search output: { "content": [ { "title": "Step 3.5 Flash - MathArena", "url": "https://matharena.ai/models/stepfun_3_5_flash", "text": "Step 3.5 Flash benchmarks and performance metrics..." } ] }
Agents can use these tools directly: // In an agent session /exec exa-search web_search_exa '{"query":"latest news"}' // Or via API { "sessionTarget": "isolated", "payload": { "kind": "agentTurn", "message": "Search for recent AI developments using exa-search" } }
Rate limits apply based on your Exa plan The MCP server uses Server-Sent Events (SSE) streaming; the wrapper handles this All tools accept various optional parameters; see Exa docs for full schema Errors are returned with proper exit codes and messages to stderr
"EXA_API_KEY not set" Ensure the environment variable is exported in the same session where OpenClaw runs If using systemd/systemctl, set the key in the service file or /etc/environment "406 Not Acceptable" The tool already sets the correct Accept header; this shouldn't occur in the wrapper Empty or no results Verify your API key has credits/quota Check the Exa dashboard: https://dashboard.exa.ai
Exa MCP Docs: https://exa.ai/docs/reference/exa-mcp MCP Server: https://mcp.exa.ai/mcp API Keys: https://dashboard.exa.ai/api-keys
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.