Tavily + Grok Bot
How to connect Tavily to Grok Bot
Connect Tavily to Grok Bot through Agent200's MCP server: no separate key, ready-made tools and one API key.
On this page
Overview
This guide connects Tavily to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in Tavily with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Grok Bot with your Agent200 API key. Tavily is reached with that key, so there is no separate Tavily key to manage.
- Connector
- Tavily
- Works with
- Grok Bot ยท 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.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Tavily to Grok Bot
-
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 Grok Bot 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: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.
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, Grok Bot calls an Agent200 tool for Tavily, such as
tavily_search.
If Grok Bot 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 Grok Bot.
Goal: connect Tavily to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/tavily/framework/grok-bot/ 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 Grok Bot'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 Grok Bot: 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 Grok Bot'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, Grok Bot 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/grok-bot.md
Tavily tools Grok Bot 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 Grok Bot
In your own words, for something in Tavily.
-
02
Grok Bot 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
Grok Bot 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
The server cannot be saved, or shows Disabled by team admin
Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.
Calls fail on a team with a network allowlist
If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.
The connector shows Needs auth, or tools return 401
Check the Authorization header is exactly Bearer, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.
The Bot cannot see the Tavily tools
Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.
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 Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.