Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Give an agent live web search, page extraction, site mapping, crawling and cited research.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Tavily MCP server gives Claude, ChatGPT or any MCP-compatible agent live access to the open web. Five tools cover search, single-page extraction, site mapping, site crawling and multi-step cited research. Every call is metered in Tavily credits, and the costs are not close to equal — one research request can spend more than a hundred searches.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
tavily_research has a 250-credit ceiling per request. Tavily documents 15–250 credits for pro and 4–110 for mini. Four maximum-cost pro calls exhaust the free monthly allowance.max_depth reaches 5 and max_breadth reaches 500 per level. limit has a documented minimum of 1 and no documented maximum.allow_external defaults to true. Results can include links beyond the domain you named unless you constrain select_domains or exclude_domains.tavily_extract caps at 20 URLs per call. Tavily's API reference states the list must not exceed 20.prompts/list, so we cannot say whether the server serves any.It depends entirely on the tool. Tavily's pricing page prices a basic search at 1 credit and an advanced search at 2. Extract costs 1 credit per 5 successful URLs, or 2 if advanced. Map costs 1 credit per 10 pages. Crawl bills mapping plus extraction together. Research is the outlier, from 4 to 250 credits per request.
Yes. Tavily documents dynamic pricing with per-request boundaries, and the ceiling is high: a request using the pro model consumes between 15 and 250 credits, while mini runs from 4 to 110. On the free 1,000-credit monthly plan, four maximum-cost pro calls would consume the entire month. The agent chooses, not you.
It crawls a site, and its documentation never states that its own crawler obeys robots.txt. Crawl defaults are depth 1, breadth 20 and a 50-link cap, but the schema allows depth 5, breadth 500 and no documented maximum on the total. Tavily's crawl best-practices page tells readers to respect robots.txt — advice to you, not a claim about itself.
Its documentation makes no such claim. Anthropic's directory description advertises PII redaction and prompt injection protection, but a full-text search of Tavily's own documentation on 2026-08-19 found zero mentions of injection, sanitisation or redaction. Treat every page these tools return as untrusted text entering the model's context, because nothing documents otherwise.
Either works. Tavily documents an API key passed as a URL query parameter or an Authorization header, and OAuth 2.0 as the alternative that keeps the key out of the URL. Under OAuth, Tavily selects which key to bill by name, preferring one called `mcp_auth_default` in your personal account over the same name on a team.
Partly. Tavily documents keyless access to the remote MCP server, but it covers Search and Extract only — Crawl, Map and Research all require an API key. A free key grants 1,000 credits per month with no credit card. Keyless access is rate-limited and intended for exploration rather than production traffic.
They differ per endpoint. Tavily documents 100 requests per minute on development keys and 1,000 on production keys as the default. Crawl is capped at 100 per minute on both, and Research at just 20 per minute on both. Exceeding a limit returns HTTP 429 with a `retry-after` header giving the seconds to wait.
.md suffix; this is the documentation URL Anthropic's directory publishes) · retrieved 2026-08-19docs.tavily.com/robots.txt allows the docs path and carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis is expressly permitted on all three axes (fetched 2026-08-19). The marketing host www.tavily.com/robots.txt allows AI crawlers by name and disallows only /api/, /legal/ and one thank-you path. mcp.tavily.com serves no robots.txt (404) · retrieved 2026-08-19POST to the endpoint returns HTTP 401 with www-authenticate: Bearer resource_metadata="https://mcp.tavily.com/.well-known/oauth-protected-resource/mcp" and no scope parameter · retrieved 2026-08-19Connect Tavily once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.