Exa MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | Yes | Your Exa API key from dashboard.exa.ai/api-keys |
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: one is specialized for programming-related searches (code context, libraries, SDKs, APIs), while the other is for general web searches and URL scraping. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the query content.
Both tools follow a consistent naming pattern: they use snake_case and include 'exa' as a suffix (get_code_context_exa, web_search_exa). The verbs 'get' and 'search' are appropriate and distinct, and the naming structure is predictable across the tool set.
With only 2 tools, the server feels thin for a general-purpose search domain, as it might lack coverage for other potential use cases like news, images, or specialized data queries. However, the tools are well-scoped for code and web searches, so it's borderline but not severely mismatched.
The tools cover core search functionalities for programming and general web content, with no dead ends. A minor gap exists in not having tools for other search types (e.g., image search or advanced filtering), but agents can likely work around this by using the provided tools effectively.