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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago