Summary
The choice of search mode is made in the tool name, not in a parameter.
search, searchContext and searchQNA stand for different intents — results, context, an answer — so a model picks the shape it wants rather than tuning options on one endpoint. extract is the other half: hand it URLs you already hold and it returns their processed content. Each call carries an options object next to the query, which is where anything finer is set.
What it is
A Tavily API client wrapping its search endpoints and its URL content extraction.
What you get
- A basic web search returning title, content and URL for every result.
- A context-aware search, tuned for retrieving contextually relevant results.
- A question-answering search, for direct questions that want a specific answer.
- Content extraction from a list of URLs, up to 20 of them in one call.
Requirements
TAVILY_API_KEY for a Tavily account.
Setup effort
One command plus a key — npx @mcptools/mcp-tavily, then supply credentials
