Tavily + Claude Duet
How to connect Tavily to Claude Duet
Connect Tavily to Claude Duet through Agent200's MCP server: no separate key, ready-made tools and one API key.
On this page
Overview
This guide connects Tavily to Claude Duet through Agent200's MCP server. When you finish, Claude Duet can search, read and act in Tavily with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Claude Duet with your Agent200 API key. Tavily is reached with that key, so there is no separate Tavily key to manage.
- Connector
- Tavily
- Works with
- Claude Duet ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 2 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Tavily enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Claude Duet, with custom MCP servers allowed. Claude Duet is a research preview for Pro, Max and Ultra users in the US, by invitation. It uses the connectors of your Claude account, and sending an API key needs Claude's Request headers option.
Connect Tavily to Claude Duet
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude Duet in the next step, as "Authorization: Bearer <your key>". One key covers Tavily and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Add Agent200 as a custom connector in Claude
Duet has no connector settings of its own: it uses those of your Claude account. In Claude, go to Customize > Connectors, choose Add > Add custom connector, enter the server URL, choose No sign-in and add the
authorizationrequest header withBearerand your key.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
3
Step 3: Use it from Duet
Open Claude Duet with the same Claude account. The connectors set up in Claude are there from your first message; manage them in your Claude settings.
-
4
Step 4: Approve actions when Duet asks
Duet asks before it sends a message, pays, signs or deletes anything. If you cannot approve right away, it finishes the rest and brings the approval back later.
Test your connection
Run one request to check everything is wired up.
Ask
What changed in the EU AI Act this month?
What should come back
- An answer built from Tavily results.
-
Behind the scenes, Claude Duet calls an Agent200 tool for Tavily, such as
tavily_search.
If Claude Duet says it has no Tavily tool, check that Tavily is enabled for your project in the dashboard.
Get your API key
Create a key in the Agent200 dashboard. It reaches Tavily and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Tavily to Claude Duet.
Goal: connect Tavily to Claude Duet with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/tavily/framework/claude-duet/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude Duet's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Tavily is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude Duet: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude Duet's exact menus or commands. 4. Check it works with this request: "What changed in the EU AI Act this month?" What should come back: - An answer built from Tavily results. - Behind the scenes, Claude Duet calls an Agent200 tool for Tavily, such as `tavily_search`. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /tools/tavily/framework/claude-duet.md
Tavily tools Claude Duet can call
-
Search the web
Readtavily_searchSearch the web and get ranked results with content.
-
Extract a page
Readtavily_extractRead the main content of a web page.
No tool matches that search.
How it works
-
01
You ask Claude Duet
In your own words, for something in Tavily.
-
02
Claude Duet picks a tool
It sees the Tavily tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Tavily with your Agent200 API key, within the endpoints your project allows.
-
04
Claude Duet answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
Duet does not see the Agent200 connector
Duet must run on the same Claude account where you added the connector. Check it is listed under Customize > Connectors in Claude.
Scheduled tasks do not call Agent200
Run the task while you are in the conversation. For unattended work, build the agent with the Agent200 SDK.
There is no Request headers option in Claude
Request headers are a Claude beta that only some accounts have, and Duet has no key field of its own. Use Claude Code, or the Agent200 SDK.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Tavily and the tools you need are enabled in the dashboard's Connectors settings.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Claude Duet's MCP settings, and stop using the old one. Paste the key only into Claude Duet's settings, never into a chat.