Exa MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_search_exaA | Search the web using Exa AI - performs real-time web searches and can scrape content from specific URLs. Supports configurable result counts and returns the content from the most relevant websites. |
| get_code_context_exaA | Search and get relevant context for any programming task. Exa-code has the highest quality and freshest context for libraries, SDKs, and APIs. Use this tool for ANY question or task for related to programming. RULE: when the user's query contains exa-code or anything related to code, you MUST use this tool. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| web_search_help | Get help with web search using Exa |
| code_search_help | Get help finding code examples and documentation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tools_list | List of available Exa tools and their descriptions |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_code_context_exa is specialized for programming-related searches with high-quality, fresh context for code, libraries, SDKs, and APIs, while web_search_exa is a general web search tool for real-time information and URL scraping. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the query content.
Both tools follow a consistent naming pattern: they use snake_case and start with a verb (get, search) followed by a noun (code_context, web), with a suffix (_exa) to indicate the server. This uniformity makes the tool names predictable and easy to understand, enhancing usability.
With only 2 tools, the server feels thin for its apparent scope of providing search capabilities via Exa AI. While the tools cover distinct areas (code and general web), a typical search server might benefit from additional tools for more granular operations (e.g., filtering, advanced queries) or other domains, making this count borderline too few for robust functionality.
The server covers basic search needs with tools for code-specific and general web searches, but there are notable gaps. For example, it lacks tools for updating or managing search results, handling different content types beyond code and web pages, or providing configuration options beyond result counts. This limits the surface for more complex agent workflows, though core search functionality is present.