Which integrations are available for this server?

Provides tools to search for code examples from GitHub repositories through Exa's search capabilities. Provides tools to search for code examples and solutions from Stack Overflow through Exa's search capabilities.

How do I use mcp-exa?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-exa search for recent research papers on transformer models" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

mcp-exa

by daedalus

Overview Schema Related Servers Score Discussions

Python

Remote

MCP Exa

A Python MCP server that exposes Exa search capabilities (no API key required)

PyPI Python Coverage Ruff

mcp-name: io.github.daedalus/mcp-exa

Install

pip install mcp-exa

Related MCP server: ReActMCP Web Search

Usage

No API key required. The server uses Exa's public MCP endpoint.

Run the MCP server:

mcp-exa

Or use as a module:

python -m mcp_exa

Configuration

Available Tools

The server exposes the following MCP tools:

Tool	Description
`web_search_exa`	Search the web for any topic
`get_code_context_exa`	Find code examples from GitHub, Stack Overflow
`crawling_exa`	Get full content from a specific URL
`web_search_advanced_exa`	Advanced search with filters

MCP Client Configuration

Claude Desktop

Add to your config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "exa": {
      "command": "mcp-exa"
    }
  }
}

OpenCode

Add to your opencode.json:

{
  "mcp": {
    "exa": {
      "type": "stdio",
      "command": "mcp-exa",
      "enabled": true
    }
  }
}

Development

git clone https://github.com/daedalus/mcp-exa.git
cd mcp-exa
pip install -e ".[test]"

# run tests
pytest

# format
ruff format src/ tests/

# lint
ruff check src/ tests/

# type check
mypy src/

Available Tools

9 tools

answerB

Generate an answer to a query using Exa's search and LLM capabilities.

ParametersJSON Schema

Name	Required	Description
`query`	Yes	The query to answer.
`text`	No	Whether to include full text in the results.
`system_prompt`	No	A system prompt to guide the LLM's behavior.
`model`	No	The model to use for answering (default: exa).
`output_schema`	No	JSON schema for structured output.
`user_location`	No	Two-letter ISO country code for user location.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must fully disclose behavior. It mentions using 'search and LLM capabilities' but does not detail how the tool works (e.g., modifies data, auth needs, rate limits, or whether it returns citations). This is insufficient for a tool with complex capabilities.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with 14 words, front-loaded with the core action. Every word is necessary and there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 6 parameters (including output_schema and system_prompt) and sibling tools like stream_answer, the description is incomplete. It does not explain the output format, when to use structured output, or how it differs from streaming, leaving agents without enough context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already describes each parameter. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Generate an answer' and the resource 'a query using Exa's search and LLM capabilities,' which distinguishes it from sibling tools like 'search' (which likely only searches) or 'stream_answer' (which suggests streaming).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'stream_answer' or 'search.' It does not mention prerequisites, when not to use it, or context for choosing this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

find_similarC

Find pages similar to a given URL using Exa.

ParametersJSON Schema

Name	Required	Description
`url`	Yes	The URL to find similar pages for.
`num_results`	No	Number of results to return.
`contents`	No	Options for retrieving page contents. Use False to disable.
`include_domains`	No	Domains to include in the search.
`exclude_domains`	No	Domains to exclude from the search.
`start_crawl_date`	No	Only links crawled after this date (YYYY-MM-DD).
`end_crawl_date`	No	Only links crawled before this date (YYYY-MM-DD).
`start_published_date`	No	Only links published after this date (YYYY-MM-DD).
`end_published_date`	No	Only links published before this date (YYYY-MM-DD).
`include_text`	No	Strings that must appear in the page text.
`exclude_text`	No	Strings that must not appear in the page text.
`exclude_source_domain`	No	Whether to exclude the source domain.
`category`	No	Data category to focus on.
`flags`	No	Experimental flags for Exa usage.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not mention any behavioral traits such as rate limits, data consumption, or whether results are cached. The tool performs a network operation, but this is not disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence without fluff, but it may be too terse for the complexity of the tool. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 14 parameters and an output schema, the description is too brief to provide sufficient context. More information about typical usage or result format would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema already documents all parameters. The description adds no additional meaning beyond 'using Exa'. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool finds pages similar to a given URL using Exa, with a specific verb and resource. However, it does not elaborate on the similarity algorithm or distinguish from related tools like search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like search, get_contents, or answer. The description lacks context on prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_contentsB

Retrieve contents for a list of URLs using Exa.

ParametersJSON Schema

Name	Required	Description	Default
`urls`	Yes	A single URL or list of URLs to retrieve contents from.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits but does not mention read-only nature, rate limits, authentication needs, or error handling. 'Retrieve contents' is minimal and leaves the agent uninformed about side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words. Information is front-loaded and directly conveys the core action. Efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, has output schema), the description provides the minimal necessary information about what the tool does. However, it lacks context on output format or edge cases, relying on the output schema for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no meaning beyond the schema's parameter description; it does not clarify acceptable URL formats, limits, or expected behavior for invalid inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves contents for URLs using Exa, specifying verb and resource. It distinguishes from siblings like search and find_similar by focusing on content retrieval rather than searching or finding similar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool over alternatives (e.g., search or find_similar). The description simply states what it does without suggesting use cases or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research_createB

Create a new research request using Exa.

ParametersJSON Schema

Name	Required	Description
`instructions`	Yes	The research instructions describing what to research.
`model`	No	The model to use ('exa-research-fast', 'exa-research', 'exa-research-pro').
`output_schema`	No	JSON schema for structured output format.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description lacks behavioral details beyond the basic creation action. With no annotations, it should disclose whether the request is asynchronous, how to check status, or if it requires polling. It fails to mention any side effects, authentication needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence with no unnecessary words. While it is concise, it could be improved by adding a brief sentence about usage context without sacrificing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description does not explain what the tool returns (e.g., request ID or status). It also fails to mention that the request is created asynchronously and must be polled or retrieved via sibling tools. This leaves the agent without key information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides descriptions for all 3 parameters (100% coverage), so the description adds no additional meaning. Baseline of 3 is appropriate as the schema already explains the parameters sufficiently.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new research request using Exa,' which specifies the verb, resource, and platform. It distinguishes this tool from siblings like research_get, research_list, and research_poll_until_finished, which handle different operations on research objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use the tool (to create a research request), but it does not provide explicit guidance on when not to use it or suggest alternatives. No exclusions or context about prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research_getB

Get a research request by ID using Exa.

ParametersJSON Schema

Name	Required	Description
`research_id`	Yes	The unique identifier of the research task.
`events`	No	Whether to include events in the response.
`output_schema`	No	Optional Pydantic model for typed output validation.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description only mentions 'using Exa' but no behavioral traits like read-only, authentication needs, or rate limits. The brief description does not compensate for the lack of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, efficient sentence. No wasted words, front-loaded with action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values are covered. The simple purpose is clear, but it could mention that it retrieves a single item. Still, it's fairly complete for a get-by-ID tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with adequate parameter descriptions. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a research request by ID using Exa' clearly states the action (get), the resource (research request), and the method (by ID). It distinguishes from siblings like research_list (list all) and research_create (create).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. For example, it doesn't mention that research_poll_until_finished is for awaiting completion, or that research_list is for browsing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research_listC

List research requests using Exa.

ParametersJSON Schema

Name	Required	Description	Default
`cursor`	No	Pagination cursor from a previous response.
`limit`	No	Maximum number of results to return.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description alone must disclose behavior. It fails to mention that results are paginated (despite cursor/limit parameters), whether it is read-only, or any side effects. The lack of behavioral detail is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (5 words), which sacrifices necessary details. While not verbose, it under-specifies the tool's capabilities and usage, making it less useful than a moderately longer description would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, return values need not be explained. However, pagination behavior (default limit, cursor usage) is entirely omitted, and no context is provided about the scope of listed requests (e.g., all by user or workspace). This makes the description incomplete for a list tool with pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents cursor and limit fully. The description adds no extra meaning beyond 'List research requests using Exa,' which does not explain how parameters affect results. Baseline 3 is appropriate as the schema bears the burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it 'List[s] research requests using Exa,' indicating a listing operation on a specific resource. It effectively distinguishes from siblings like 'research_create' and 'research_get' by using the verb 'list.' However, the term 'research requests' is ambiguous without further context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives (e.g., research_get for a single request, research_poll for polling status). It does not mention prerequisites or limitations, leaving the agent without context to choose appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

research_poll_until_finishedA

Poll until research is finished using Exa.

ParametersJSON Schema

Name	Required	Description
`research_id`	Yes	The unique identifier of the research task.
`poll_interval`	No	Milliseconds between polling attempts (default: 1000).
`timeout_ms`	No	Maximum time to wait in milliseconds (default: 600000).
`events`	No	Whether to include events in the response.
`output_schema`	No	Optional Pydantic model for typed output validation.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavior. It states polling until finished, but does not explain that it blocks, returns the final result, or handles timeouts/errors. The input schema provides poll_interval and timeout_ms, which partially compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise at one sentence. It is front-loaded and clear, but could include more useful context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output_schema parameter and siblings like research_create and research_get, the description is minimally complete. It does not explain that it returns the research result, which would help an agent understand the workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter having a description. The tool description adds no additional parameter meaning beyond what the schema provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Poll until research is finished using Exa' clearly states the action (poll), the resource (research), and the condition (until finished). It distinguishes itself from sibling tools like research_create (creation), research_get (single fetch), and research_list (listing) by emphasizing the polling behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after creating a research task, but does not explicitly state when to use this tool versus alternatives like research_get for manual polling or other research tools. No exclusion or alternative names are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchC

Perform a web search using Exa.

ParametersJSON Schema

Name	Required	Description
`query`	Yes	The search query string.
`num_results`	No	Number of search results to return (default: 10).
`contents`	No	Options for retrieving page contents. Use False to disable.
`include_domains`	No	Domains to include in the search.
`exclude_domains`	No	Domains to exclude from the search.
`start_crawl_date`	No	Only links crawled after this date (YYYY-MM-DD).
`end_crawl_date`	No	Only links crawled before this date (YYYY-MM-DD).
`start_published_date`	No	Only links published after this date (YYYY-MM-DD).
`end_published_date`	No	Only links published before this date (YYYY-MM-DD).
`include_text`	No	Strings that must appear in the page text.
`exclude_text`	No	Strings that must not appear in the page text.
`type`	No	Search type - 'auto', 'fast', 'deep', 'deep-reasoning', or 'instant'.
`category`	No	Data category to focus on (e.g., 'company', 'news', 'research_paper').
`flags`	No	Experimental flags for Exa usage.
`moderation`	No	If True, moderate search results for safety.
`user_location`	No	Two-letter ISO country code for user location.
`additional_queries`	No	Alternative query formulations for deep search.
`output_schema`	No	JSON schema for deep search structured output.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It only says 'using Exa,' revealing the service provider but omitting essential details like rate limits, authentication, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but too minimal for a tool with 18 parameters. It front-loads the purpose but lacks structure and detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (18 parameters, output schema exists), the description is incomplete. It fails to explain the return format, output schema usage, or how to combine filters, relying entirely on the input schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not add any parameter meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Perform a web search using Exa,' which identifies the verb and resource. However, it does not differentiate from sibling tools like 'answer' or 'find_similar' that may also involve searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description only states what it does without any context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

stream_answerC

Generate a streaming answer response using Exa.

ParametersJSON Schema

Name	Required	Description
`query`	Yes	The query to answer.
`text`	No	Whether to include full text in the results.
`system_prompt`	No	A system prompt to guide the LLM's behavior.
`model`	No	The model to use for answering.
`output_schema`	No	JSON schema for structured output.
`user_location`	No	Two-letter ISO country code for user location.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description bears full burden for behavioral disclosure. It only mentions 'streaming' without explaining implications (e.g., chunked responses, early termination, connection handling). No information on side effects, authentication, rate limits, or reversibility is provided. The agent lacks critical awareness of how the tool behaves during execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but overly minimal. While brevity is valued, the content is insufficient to inform the agent about streaming behavior, usage, or parameters. It lacks front-loaded key details and structure, sacrificing completeness for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 6 parameters, streaming behavior, an output schema, and several sibling tools. The description does not explain the streaming mechanism, the role of optional params (e.g., system_prompt, output_schema), or how it differs from 'answer'. Given the complexity, the description is incomplete and leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all 6 parameters, so the schema already documents parameter meaning adequately. The description adds no additional semantic context beyond the schema. With full coverage, baseline is 3; the description does not degrade or enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Generate a streaming answer response using Exa,' which indicates the tool produces streaming answers via Exa. However, it is somewhat vague and essentially restates the tool name without specifying what constitutes an 'answer response' or how it differs from a non-streaming version. The mention of 'streaming' provides minimal distinction from the sibling tool 'answer'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'answer'. The description does not specify contexts (e.g., real-time vs. batch, latency-sensitive tasks) or when streaming is beneficial. The agent receives no help in selecting the appropriate tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

9 tool updatesv0.1.2Apr 27, 2026
- First observedanswer
- First observedfind_similar
- First observedget_contents
- First observedresearch_create
- First observedresearch_get
- First observedresearch_list
- First observedresearch_poll_until_finished
- First observedsearch
- First observedstream_answer

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Disambiguation5/5

Each tool targets a distinct operation: search, get contents, find similar, answer (both streaming and non-streaming), and CRUD for research requests. No overlapping purposes.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., research_create, get_contents). 'answer' and 'stream_answer' are verbs without a noun suffix, but the pattern is clear overall.

Tool Count5/5

9 tools is well within the optimal 3-15 range. Each tool serves a clear function without redundancy.

Completeness4/5

Covers search, content retrieval, similarity, answer generation, and research lifecycle. Minor gap: no explicit update or delete for research requests, but research is likely immutable and poll_until_finished covers progression.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

exa A
ai.exa
Fast, intelligent web search and web crawling. New mcp tool: Exa-code is a context tool for coding
Search Web Scraping Developer Tools
294,963
Serper A
io.github.pipeworx-io
Serper MCP — wraps the Serper Google Search API (serper.dev)
Search RAG Systems
342
MCP Aggregation Gateway — 22k+ MCP search & call A
cn.pianam.mcp
One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key.
31
mcp A
ai.llmse
Public MCP server for the LLM Search Engine
Search RAG Systems Developer Tools
102

Related MCP Servers

metasearch-mcp
Search RAG Systems
YeonwooSung
A
license
Not graded
quality
D
maintenance
MCP server for using various search tools like Tavily API. Planning to support various search tools (i.e. wiki search, searxng, etc)
Updated a year ago (2025-04-16 13:05 UTC)
3
MIT
ReActMCP Web Search
Search RAG Systems
mshojaei77
A
license
Not graded
quality
C
maintenance
An MCP server that integrates real-time web search capabilities into AI assistants using the Exa API, providing both basic and advanced search functionality with formatted markdown results.
Updated a month ago (2026-07-22 19:21 UTC)
143
MIT
Swift Poe Search MCP
Search AI & Machine Learning Research & Data
mehmetbaykar
A
license
Not graded
quality
F
maintenance
An MCP server that integrates with Poe's API to provide AI-powered search and research tools from Perplexity, Reka, Exa, and Linkup.
Updated 2 months ago (2026-07-15 22:45 UTC)
24
8
MIT
gemini-deep-research-mcp
Search Browser Automation AI & Machine Learning
bharatvansh
A
license
A
quality
A
maintenance
An MCP server that exposes Gemini's Deep Research Agent for comprehensive web research.
Updated 16 days ago (2026-08-21 05:19 UTC)
2
42
4
MIT

Appeared in Searches

Comparison of Exa MCP Server and Tavily search tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daedalus/mcp-exa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server