← All integrations

Tavily MCP

5 operations0 webhooks

MCP server exposing Tavily web search tools for AI agent research workflows.

Supported operations

  • CrawlRead-only

    Crawl a site from a start URL with configurable depth and breadth

  • ExtractRead-only

    Extract page content from one or more URLs as markdown or plain text

  • MapRead-only

    Map a site's structure from a start URL and return its URLs

  • ResearchRead-only

    Run comprehensive multi-source research on a topic and return a cited report

  • SearchRead-only

    Search the web with Tavily and return ranked snippets with source URLs

FAQ

Install corsair and @corsair-dev/tavilymcp, add the Tavily MCP plugin, and connect with an API key. Then call methods like corsair.tavilymcp.api.tavily.crawl() from your app. Corsair syncs data per tenant.

Yes. Tavily MCP requires an API key from your Tavily MCP account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Tavily MCP, GitHub, Notion, Stripe, and the rest. Trigger Tavily MCP from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for mcp server exposing tavily web search tools for ai agent research workflows. Common builds include sync jobs, admin tooling, and agents that call Tavily MCP APIs from your backend. Local DB entities let you query synced Tavily MCP records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Tavily MCP API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/tavilymcp in the open repo. When Tavily MCP ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Tavily MCP data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Tavily MCP data on your behalf.