Add Exa Search MCP Server to Marketplace

[10ishq]

What kind of feedback?

Suggestion for new MCP server

Item Type (if applicable)

MCP Server

Item Name (if applicable)

Exa

Description

Exa is a search engine built for AI. The Exa MCP server gives Roo Code agents real-time web search, code context retrieval, company research, and web crawling capabilities.

GitHub: https://github.com/exa-labs/exa-mcp-server (4,100+ stars, MIT license)
Website: https://exa.ai
npm: exa-mcp-server
Remote endpoint: https://mcp.exa.ai/mcp (Streamable HTTP — no local install needed)

MCP Configuration (Remote — recommended)

{
  "mcpServers": {
    "exa": {
      "type": "streamable-http",
      "url": "https://mcp.exa.ai/mcp"
    }
  }
}

MCP Configuration (Local via npm)

{
  "mcpServers": {
    "exa": {
      "command": "npx",
      "args": ["-y", "exa-mcp-server"],
      "env": {
        "EXA_API_KEY": "your-api-key"
      }
    }
  }
}

Available Tools

Tool	Description
web_search_exa	Real-time web search with AI-optimized results
research_paper_search_exa	Academic paper search across scholarly sources
company_research_exa	Deep company research by crawling company websites
crawling_exa	Extract content from specific URLs
competitor_finder_exa	Find competitors for a given company
linkedin_search_exa	Search LinkedIn profiles and companies
get_code_context_exa	Retrieve relevant code context for coding tasks
web_search_advanced_exa	Advanced search with fine-grained filters

Exa is already listed on the Official MCP Registry (ai.exa/exa), awesome-mcp-servers, Smithery, PulseMCP, Glama, MCP.so, and the Cline MCP Marketplace.

Additional Details (optional)

API keys available at https://dashboard.exa.ai/api-keys

Checklist

• I've searched existing issues for duplicates

[roomote-v0]

Thanks for the suggestion! I looked into this and wanted to share what I found.

The Roo Code marketplace items (including MCP servers) are served from a remote API endpoint, not from files within this repository. The extension's RemoteConfigLoader fetches MCP listings from the Roo Code API at runtime. This means adding a new MCP server to the marketplace is a backend/content management change on the API side, not a code change in this repo.

Because of this, a pull request to this repository would not be the right path for adding Exa to the marketplace catalog. This would need to be handled by the Roo Code team on the server side where marketplace items are managed.

That said, the information provided in this issue (configurations, available tools, links) is thorough and should make it straightforward for the team to evaluate and add Exa if they choose to.

I'll leave this for the maintainers to triage accordingly.