Exa MCP integration for AI agents.
Connect AI agents to Exa through 4 structured actions, including find similar, answer, and get contents. Review authentication, inputs, workflows, and safety…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Exa integration exposes
The Exa Agent App exposes 4 provider-backed actions for ai and data work. Its current contract lets an authorized agent find pages similar to a given url and optionally enrich them with contents, generate a citation-backed answer from exa search results, and fetch text, highlights, or summaries from exa for urls or document ids. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Exa account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Exa capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_similarREADFind pages similar to a given URL and optionally enrich them with contents.
INPUTS: url / excludeSourceDomain / numResults / includeDomains / excludeDomains
answerREVIEWGenerate a citation-backed answer from Exa search results.
INPUTS: query / text
get_contentsREADFetch text, highlights, or summaries from Exa for URLs or document IDs.
INPUTS: urls / ids / text / highlights / summary
searchREADSearch the web with Exa and optionally enrich each result with contents.
INPUTS: query / additionalQueries / type / category / numResults
INPUT CONTRACTS
Know what the action needs before it runs.
find_similar
urlREQUIRED- The URL used to find similar pages.
excludeSourceDomainOPTIONAL- Whether to exclude results from the same domain as the input URL.
numResultsOPTIONAL- The number of similar results to return, up to 100.
includeDomainsOPTIONAL- Only return results from these domains.
excludeDomainsOPTIONAL- Exclude results from these domains.
answer
queryREQUIRED- The question or prompt Exa should answer.
textOPTIONAL- Whether citations should include the full source text.
get_contents
urlsREQUIRED- The list of URLs to retrieve content for.
idsOPTIONAL- Deprecated. A backward-compatibility list of Exa document IDs.
textOPTIONALhighlightsOPTIONALsummaryOPTIONAL- Configuration for an Exa summary response.
search
queryREQUIRED- The search query to send to Exa.
additionalQueriesOPTIONAL- Additional query variations to use with deep or deep-reasoning search.
typeOPTIONAL- The Exa search mode to execute.
categoryOPTIONAL- The Exa category used to narrow search results.
numResultsOPTIONAL- The number of search results to return, up to 100.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Similar
Find pages similar to a given URL and optionally enrich them with contents. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_similarVerify with Get Contents
Fetch text, highlights, or summaries from Exa for URLs or document IDs. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contentsSAFETY BOUNDARY
Operate Exa with explicit limits
- Authorize Exa with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Exa data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Exa rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Exa task completed successfully.
CONNECTION MODEL
API key
Exa API key used with the x-api-key request header. Get it from the Exa Dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Exa.