Skip to main content
Gumloop includes Exa as a built-in MCP integration. Add it to an agent or Agent Node to search the web, extract pages, find related sources, and produce citation-backed answers inside a workflow.

​
Add Exa to a Gumloop agent

1

Open the agent

Open your agent’s configuration, then select Add tools → Connect an app with MCP.
2

Connect Exa

Search for Exa, select the integration, and complete the authentication flow.
3

Choose the tools

Open the connected Exa integration and enable only the tools the agent needs. This makes tool selection clearer and prevents the agent from calling unrelated actions.
4

Test the connection

Ask the agent:
Review the run to confirm that the agent called Exa and returned cited sources.

​
Available tools

For a conversational agent, enable Search, Get Contents, and Answer first. Add the remaining tools only when the workflow requires them.

​
Use Exa in a workflow

​
Agent Node

Add an Agent Node to a deterministic Gumloop flow and attach Exa as one of its tools. The node can decide whether to search, retrieve complete pages, or chain several Exa calls before passing its output to the next workflow step. This works well for:
  • enriching CRM or spreadsheet rows with current web evidence
  • monitoring news and sending a sourced summary to Slack or email
  • researching companies before routing records to a sales workflow
  • comparing products and writing the result to a document

​
Reusable custom MCP node

For a single repeatable action, create a dedicated node:
  1. Open the node library and find Exa.
  2. Select Create a node with AI.
  3. Describe one action, such as Search for funding announcements from the past seven days.
  4. Test the generated node, verify its inputs and outputs, then save it.
Use an Agent Node when the task requires dynamic planning or multiple tools. Use a custom MCP node when the same Exa operation should run predictably on every item.

​
Prompt patterns

​
Troubleshooting

Reopen the agent’s MCP tools, confirm that Exa is connected, and enable the required tool. A connected integration can still have individual tools disabled.
Make the request explicit about whether it should search, read known URLs, find similar pages, or answer from sources. Disable Exa tools the agent does not need for that workflow.
Replace the general-purpose agent step with a custom Exa MCP node whose inputs and task are fixed.

​
Resources

Gumloop Exa integration

Review Gumloop’s current tools and Agent Node workflow.

Exa MCP server

Understand the Exa tools exposed through MCP.

Exa Search

Learn how to shape search queries and returned contents.
Last modified on September 15, 2026