Exa Search

Created By
treea year ago
Overview

Exa Search is a Model Context Protocol (MCP) server that enables AI assistants like Claude to utilize the Exa AI Search API for real-time web searches in a secure manner.

To use Exa Search, you can connect to the hosted MCP server using your Exa API key or run it locally via npm. Configuration is done through the Claude Desktop app or directly via command line.

  • Real-time web search capabilities for AI models.
  • Multiple tools for specialized searches including academic papers, company research, and web crawling.
  • Easy integration with Claude Desktop and other AI assistants.
  1. Conducting real-time web searches for AI-driven applications.
  2. Researching academic papers and extracting relevant information.
  3. Gathering detailed company information for business analysis.
  • How do I get my Exa API key?

You can obtain your Exa API key from the Exa dashboard at dashboard.exa.ai/api-keys.

  • Can I run Exa Search locally?

Yes, Exa Search can be run locally using npm commands.

  • What tools are available with Exa Search?

Exa Search includes tools for web search, research paper search, company research, and more.

Server Config

{
  "mcpServers": {
    "exa": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "exa",
        "--key",
        "f249a372-7b6e-4b96-9e5a-050c320e8b18"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tree
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago