Skip to content

Exa

Updated View as Markdown

Search the web, find similar pages and retrieve explicitly selected page contents using a customer Exa API key. Native result limits, domain filters, publication dates and content options remain visible.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Search the web with explicit result and content limits

Help me with this task in Exa: Search the web with explicit result and content limits. Ask me to choose the destination and provide the content and any required resource IDs. Show the exact proposed change for my review, then perform it only after I approve. Return the created or updated resource ID and link when supplied. If the result is uncertain, inspect it before attempting the same change again.

Explore this command: exa.search

Find pages similar to one explicit URL

Help me with this task in Exa: Find pages similar to one explicit URL. Ask me to choose the destination and provide the content and any required resource IDs. Show the exact proposed change for my review, then perform it only after I approve. Return the created or updated resource ID and link when supplied. If the result is uncertain, inspect it before attempting the same change again.

Explore this command: exa.find-similar

What you can do (3)

What you can do

Available commands: 3 (0 read, 3 write). Enable only the commands your application needs.

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Exa, then enter the issued values in the connection form below.

  1. In the Exa dashboard, open API Keys and create a key for the intended project. Review provider billing and usage limits before enabling calls. Paste it into this connection’s Exa API token field and choose search, find-similar or contents. Keep numResults small and request text only when needed; contents accepts explicit IDs and does not crawl links automatically. Save the connection, enable commands and create a separate scoped Tooluse.net API key for your AI client. Never put the Exa key in the MCP URL.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Exa API token Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "body": {
      "query": "Tooluse.net documentation",
      "numResults": 3,
      "contents": {
        "text": true
      }
    }
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Find pages similar to one explicit URL — exa.find-similar

Find pages similar to one explicit URL

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false
body.url string Required format: "uri"
body.numResults integer Optional minimum: 1; maximum: 100
body.excludeSourceDomain boolean Optional
body.contents object Optional additionalProperties: false
body.contents.text — Optional
body.contents.text boolean Optional oneOf[1]
body.contents.text object Optional oneOf[2]; additionalProperties: false
body.contents.text.maxCharacters integer Optional oneOf[2]; minimum: 1; maximum: 1000000
body.contents.text.includeHtmlTags boolean Optional oneOf[2]
body.contents.highlights object Optional additionalProperties: true
body.contents.summary object Optional additionalProperties: true
body.contents.livecrawl string Optional enum: ["never","fallback","always","preferred"]
body.contents.livecrawlTimeout integer Optional minimum: 1; maximum: 30000

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {
    "url": "https://example.com/",
    "numResults": 3
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Fetch content for explicitly selected search IDs — exa.contents

Fetch content for explicitly selected search IDs

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false
body.ids array Required minItems: 1; maxItems: 100
body.ids[] string Optional minLength: 1
body.text — Optional
body.text boolean Optional oneOf[1]
body.text object Optional oneOf[2]; additionalProperties: false
body.text.maxCharacters integer Optional oneOf[2]; minimum: 1; maximum: 1000000
body.text.includeHtmlTags boolean Optional oneOf[2]
body.highlights object Optional additionalProperties: true
body.summary object Optional additionalProperties: true
body.livecrawl string Optional enum: ["never","fallback","always","preferred"]
body.livecrawlTimeout integer Optional minimum: 1; maximum: 30000

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {
    "ids": [
      "https://example.com/"
    ],
    "text": true
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close