Skip to main content
Vercel Connect manages credentials for apps and agents that call Tavily’s MCP server or REST API. Use OAuth when each user connects their own Tavily account, or an API key for shared application access. Connect handles credentials; Eve runs agents; AI Gateway routes model requests. You can use Connect without either. For Tavily tools used directly in the AI SDK, see Vercel AI SDK.

Prerequisites

  • A Vercel account and permission to create connectors and link projects.
  • A Tavily account with credits. API-key connections also need a Tavily API key.
  • Node.js 22 or newer for the scripts below, or Node.js 24 or newer for Eve, and the Vercel CLI.

Set up the connector

1

Choose MCP or API

Open Tavily on Vercel Connect, select Create Connector, and choose your team. Select MCP for agent tools or API for direct REST calls.
Vercel Connect offering MCP and API connections for Tavily
2

Configure authentication

For MCP OAuth, keep Managed, enter a name, and continue. Vercel manages the OAuth client. For the API connection, enter your key from the Tavily dashboard.
Managed OAuth configuration with connector name and optional UID
3

Create the connector

Leave the optional icon and colors as they are, or customize them. Select Create Connector, then Continue. Copy the connector’s UID for your code; the examples use tavily/your-connector-name as a placeholder.
Optional connector branding and Create Connector button
Confirmation that the Tavily connector has been created
4

Link a project

In the connector’s Projects section, select Connect Project, choose your project, and enable Development for local testing. If it is already linked, check the enabled environments. A deployment is not required.
Tavily connector page with the Connect Project button

The Projects section of a Tavily connector; your connector name and UID will differ.

Prepare a local project

Use an existing project directory, or create one:
Select the same project you linked to the connector. vercel env pull creates .env.local with a development VERCEL_OIDC_TOKEN. Keep this file out of Git and refresh it with the same command if the token expires. See Vercel’s authentication guide.

Example usage

Find three sources about a company’s product announcements, then use the results in a news feed, account brief, or research agent. Choose the example that matches your connector.
Save this as search.mjs. The first run prints an authorization link. Open it, sign in to Tavily, approve access, and rerun the script.
search.mjs
The response contains search results with titles, URLs, and content snippets. Creating a connector does not authorize a user: the grant belongs to the same user ID used in both calls. In an application, replace local-user with the signed-in user’s ID from your server-side session.To let a model choose and call tools, follow Vercel’s AI SDK and MCP guide.

Resources