Labsco
MCP SERVER

Tavily MCP Server

by altinakseven

Web search through Tavily, with the direct answer and the sources in the same response.

Web Search Engines
Summary
Search with domain filters and the answer attached.

Beyond searching, a query here can be pinned to the domains you trust or kept away from ones you do not — the difference between an answer you can cite and one you have to go and check. The same call carries a depth switch, so a fast lookup and a careful one need only the one tool.

What it is

A single-tool server that puts Tavily's search API in front of an assistant. One call takes a query and returns ranked pages, a short direct answer where Tavily has one, and suggested follow-up questions. It is a TypeScript project you build and run from the repository against your own Tavily key, not something you pull from a package registry.

What you get
  • One search call returning ranked pages with title, URL, a content snippet, a relevance score, and a publication date where one exists
  • A direct answer to the query when Tavily has one — alongside the sources, not instead of them
  • Suggested follow-up questions with every response
  • A depth switch, so a quick lookup and a thorough sweep go through the same tool
  • Control over how many results come back
  • Domain include and exclude lists, so a query can be pinned to one documentation site or kept away from a source you distrust
Requirements

A Tavily API key of your own, supplied to the process as an environment variable. Node and npm: you clone the repository, install, build, and point your client at the built entry point — there is no package to install by name. A process manager and an optional reverse proxy are documented for leaving it running on a server.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary