BrowserAI Dev vs Exa MCP Server
A side-by-side look at the BrowserAI Dev and Exa MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BrowserAI Dev for search & data extraction work as a local process; choose Exa MCP Server for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BrowserAI Dev when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LASTSEARCH_API_KEY. - You want tools like
search, open, extract.
Choose Exa MCP Server when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
web_search_exa, web_fetch_exa.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 63/100 · Good | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | LASTSEARCH_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 20 | 5,141 |
| Directory activity | 3 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 13 | 2 |
| Full listing | View BrowserAI Dev | View Exa MCP Server |
Tools & capabilities
BrowserAI Dev tools 13
searchSearch the web for information on any topicopenFetch and parse a web page into clean textextractExtract structured claims from a pageanswerFull pipeline: search + extract + cite. `depth`: `"fast"`, `"thorough"`, or `"deep"compareCompare raw LLM vs evidence-backed answerclarityAnti-hallucination answer engine — three modes: prompt (prompts only), answer (LLM), verified (LLM + web fusion)session_createCreate a research session (persistent memory)session_askResearch within a session (recalls prior knowledge)session_recallQuery session knowledge without new web searchsession_shareShare a session publicly (returns share URL)session_knowledgeExport all claims from a sessionsession_forkFork a shared session to continue the research- +1 more on the listing page
Exa MCP Server tools 2
web_search_exaSearch the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.web_fetch_exaRead a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
BrowserAI Dev
{
"mcpServers": {
"browseai-hq-browserai-dev": {
"command": "npx",
"args": [
"-y",
"lastsearch"
],
"env": {
"LASTSEARCH_API_KEY": "YOUR_LASTSEARCH_API_KEY_HERE"
}
}
}
}
Exa MCP Server
{
"mcpServers": {
"exa-labs-exa-mcp-server": {
"command": "npx",
"args": [
"-y",
"exa-mcp-server"
]
}
}
}
Frequently asked questions
BrowserAI Dev is categorized under Search & Data Extraction and uses a local stdio subprocess. Exa MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick BrowserAI Dev for search & data extraction work and Exa MCP Server for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
BrowserAI Dev is listed as freemium — a free tier with paid plans. Auth: api key required. Exa MCP Server is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add browseai-hq-browserai-dev and exa-labs-exa-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BrowserAI Dev has a quality signal of 63/100 (Good) with 3 views, 0 installs and 20 GitHub stars. Exa MCP Server has 73/100 (Great) with 6 views, 0 installs and 5,141 GitHub stars.