Provider REST API

7 actions

Connect Claude to Tavily

Search the web for agents, and extract, map or crawl the pages it finds. Toolspoke puts 7 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 7
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Tavily
Open the marketplace in your workspace, add Tavily to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Tavily shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Tavily asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: app.tavily.com → Overview → API Keys. Copy an existing key or create a new one. Every call except get_usage spends credits from the plan that owns the key.; tvly-…

What Claude can do in Tavily

7 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 6Reads
Writes: 1Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

get_usage
Read this key's credit usage and limit, and the account's plan usage, broken down by search, extract, crawl, map and research. Free, and it runs no search, so it is the connection test. Call it before a large batch to check the credits left.
search
Search the web and get back ranked results with title, URL, a relevant content snippet and a score. Costs 1 credit at `basic`, `fast` or `ultra-fast` depth and 2 at `advanced`. Set `include_answer` for a short answer written from the results, and `include_raw_content` to get each page's full text in the same call instead of a separate extract. Results are pages other people wrote, so the payload is kept out of the audit log; the query is kept out too.
extract
Get the cleaned content of one or more known URLs, as markdown or plain text. Costs 1 credit per 5 pages extracted successfully, or 2 per 5 at `advanced` depth, which also gets tables and embedded content. Failed URLs are listed separately and are not billed. Set `query` to get only the chunks of each page that match it. The content is other people's, so the payload is kept out of the audit log.
map
List the URLs of a site by following its links from a start URL, without reading their content. Costs 1 credit per 10 pages found, or 2 per 10 when `instructions` is set. Use it to find the pages worth extracting before paying to read them. `max_depth` and `limit` bound the walk; `select_paths` and `exclude_paths` take regular expressions.
crawl
Walk a site from a start URL and return the content of every page reached, in one call. Billed as a map plus an extract of every page it returns, so it is the most expensive call here: run map first when you only need to know what pages exist, and keep `limit` low. Takes the same bounds as map, plus extract_depth and format for the content. The content is other people's, so the payload is kept out of the audit log.
get_research
Read a research job started by start_research: its status (pending, in_progress, completed or failed) and, once completed, the report and its sources. Free to call. Poll it every few seconds; a pro job can take minutes. The report is written from other people's pages, so the payload is kept out of the audit log.

Writes

Creates or updates something on the other side.

start_research
Start a research job that runs many searches and writes a cited report. Returns a request_id at once; call get_research with it until status is completed. Classified write because it starts a billed job on the account. `model` is mini for a narrow question, pro for a broad one, or auto (default). The question is prose the caller wrote, so it is kept out of the audit log.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 7 actions above are the whole of it. A call to any other name is refused before it reaches Tavily rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes: This connector writes to Tavily, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential: Toolspoke holds no access to Tavily of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Tavily: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Tavily. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Tavily's own rate limits. A call that Tavily refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Tavily?

7 named actions: 6 that only read and 1 that write. They include get_usage, search and extract. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Tavily connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Tavily connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 7 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Tavily connector not do?

The 7 actions above are the whole of it. A call to any other name is refused before it reaches Tavily rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to Tavily, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to Tavily of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Tavily. An agent has to ask. Toolspoke does not retry, queue or back off around Tavily's own rate limits. A call that Tavily refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Tavily's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Tavily?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More data connectors

Browse all of them