Exa MCP Server

Created By
it-bearda year ago
AI-powered code search MCP server using Exa API for intelligent code search and retrieval in AI assistants
Overview

what is Exa MCP Server?

Exa MCP Server is an AI-powered code search server utilizing the Exa API to offer intelligent code search and retrieval functionalities for AI assistants.

how to use Exa MCP Server?

To use Exa MCP Server, clone the repository, install the dependencies, build the project, and configure your Exa API key to start performing AI-powered code searches.

key features of Exa MCP Server?

  • AI-driven code searches using natural language queries.
  • Immediate retrieval of relevant code examples and documentation.
  • Customizable search result counts.
  • Outputs responses in JSON format with rich metadata.

use cases of Exa MCP Server?

  1. Quickly finding coding solutions and examples during software development.
  2. Assisting developers in understanding code snippets through context-relevant searches.
  3. Enhancing AI assistants' capabilities to support coding queries effectively.

FAQ from Exa MCP Server?

  • What programming languages does Exa MCP Server support for searches?

Exa MCP Server is designed to work with a variety of programming languages as long as they can be found in the searchable repository.

  • Is there a limit to the number of search results I can request?

Yes, the number of search results is configurable and can be adjusted according to user preference.

  • How do I contribute to the Exa MCP Server?

To contribute, fork the repository, create a feature branch, commit your changes, push it to your branch, and open a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
it-beard
Star
-
Language
-
License
-

Recommend Servers

View All
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