Tavily MCP exposes the Tavily web API to any Model Context Protocol client as four tools: search, extract, map, and crawl. Search returns current web results, extract pulls content from given pages, map produces a structured map of a site, and crawl walks a site systematically.
You can connect to the hosted endpoint at mcp.tavily.com without running anything locally, passing a Tavily API key in the URL or an Authorization: Bearer header, or completing an OAuth flow from clients such as Claude Code, Cursor, or the MCP Inspector. When OAuth is used, the key named mcpauthdefault in your personal account or team is selected, falling back to default and then the first available key. The server can also run locally.
Features
- tavily-search: real-time web search with parameters such as searchdepth, maxresults, and include_images
- tavily-extract: content extraction from web pages
- tavily-map: builds a structured map of a website
- tavily-crawl: systematic exploration of a site's pages
- Remote or local: a hosted endpoint or a local process
- Authentication options: API key in URL, bearer header, or OAuth
- Default parameters: a default-parameters JSON header or environment variable applies defaults to every request
- End-user identification: an optional human ID is forwarded as an X-Human-Id header and hashed server-side with SHA-256 for per-user analytics
