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 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search the web using Exa AI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity or risk of misselection. The single 'search' tool is clearly distinct by default, and its description accurately conveys its purpose.
The tool name 'search' is a clear, simple verb that matches its function. With only one tool, there is no inconsistency or mixed conventions to evaluate.
A single tool is borderline for server scope. While it may be sufficient for a dedicated search API, the thin surface limits versatility and feels minimal compared to typical MCP servers.
The server provides the core search functionality without additional operations like filtering, pagination, or result retrieval by ID. These are minor gaps that agents can likely work around, but the surface is not fully comprehensive.