tavily-fastmcp

Typed, ergonomic FastMCP server for Tavily search, extract, map, crawl, and research workflows.

It ships with:

• namespaced MCP tools like tavily.search and tavily.research
• packaged prompt profiles and large markdown system prompts
• static resources and dynamic resource templates for profiles, prompts, examples, and server catalogs
• a small direct Python API for local use without MCP
• docs, examples, CI, publishing workflow, coverage, Ruff, and mypy

Why this package

langchain-tavily already gives you the raw Tavily tools. tavily-fastmcp adds a cleaner MCP boundary around them:

• richer metadata for MCP clients
• reusable profiles for common workflows
• discoverable prompt and resource surfaces
• stable typed request/response models you can test directly
• easier LangChain + MCP composition

Tavily's official LangChain package provides the raw Tavily tools, and this package wraps them in a typed FastMCP server surface with prompts, resources, profiles, and example client configuration.

Installation

pdm add tavily-fastmcp

For LangChain helpers:

pdm add tavily-fastmcp[langchain]

For docs and development:

pdm install -G:all

Environment

Tavily uses the TAVILY_API_KEY environment variable. This package preserves that variable directly and layers package-specific settings under the TAVILY_FASTMCP_ prefix.

cp .env.example .env

Put real keys only in .env; it is ignored by Git. Keep .env.example as placeholders.

To run the opt-in live smoke test:

make test-live

Quick start

Run the MCP server

tavily-fastmcp

Or:

python -m tavily_fastmcp.server --transport stdio

Direct Python usage

from tavily_fastmcp.service import LangChainTavilyService
from tavily_fastmcp.settings import get_settings

service = LangChainTavilyService(get_settings())
response = service.search_from_model(query="latest FastMCP prompts docs")
print(response.results[0].url)

Create a FastMCP server in code

from tavily_fastmcp.server import create_server

server = create_server()

Use through LangChain over MCP

import asyncio

from langchain.agents import create_agent
from langchain_mcp_adapters.client import MultiServerMCPClient


async def main() -> None:
    client = MultiServerMCPClient(
        {
            "tavily": {
                "command": "python",
                "args": ["-m", "tavily_fastmcp.server", "--transport", "stdio"],
                "transport": "stdio",
            }
        }
    )
    tools = await client.get_tools()
    agent = create_agent(model="openai:gpt-5", tools=tools)
    result = await agent.ainvoke(
        {
            "messages": [
                {
                    "role": "user",
                    "content": "Research the best docs pages for FastMCP resource templates.",
                }
            ]
        }
    )
    print(result)


asyncio.run(main())

Build a focused research agent

Use MCP when you want the model to choose among Tavily search, extract, map, crawl, and research tools at runtime:

import asyncio

from langchain.agents import create_agent
from langchain_mcp_adapters.client import MultiServerMCPClient


async def build_agent():
    client = MultiServerMCPClient(
        {
            "tavily": {
                "transport": "stdio",
                "command": "python",
                "args": ["-m", "tavily_fastmcp.server", "--transport", "stdio"],
                "env": {"TAVILY_API_KEY": "tvly-your-key-here"},
            }
        }
    )
    tools = await client.get_tools()
    return create_agent(
        model="openai:gpt-5",
        tools=tools,
        system_prompt=(
            "Use Tavily for current web research. Prefer tavily.search for broad "
            "discovery, tavily.extract for source reading, and tavily.research "
            "when a synthesized report is requested."
        ),
    )


async def main() -> None:
    agent = await build_agent()
    result = await agent.ainvoke(
        {
            "messages": [
                {
                    "role": "user",
                    "content": "Compare three recent MCP client patterns and cite sources.",
                }
            ]
        }
    )
    print(result)


asyncio.run(main())

Included profiles and prompts

The package ships with large markdown prompts and reusable profiles for:

• router
• suite-overview
• quick-search
• tool-search
• extract-and-summarize
• tool-extract
• site-discovery
• tool-map
• site-crawl
• tool-crawl
• deep-research
• tool-research
• tool-get-research
• routing-matrix
• synthesis-policy
• mcp-usage-guide

They are exposed both as packaged markdown files and as MCP resources / prompts. The richer catalog now also includes a composite suite overview, per-tool deep guides, a routing matrix, a synthesis policy, and an MCP usage guide.

Example URIs:

• resource://tavily-fastmcp/catalog/server
• resource://tavily-fastmcp/catalog/profiles
• resource://tavily-fastmcp/profile/deep-research
• resource://tavily-fastmcp/prompt/router
• resource://tavily-fastmcp/prompt/deep-research
• resource://tavily-fastmcp/example/claude-desktop-config

The server is organized so MCP clients can discover tools, prompts, resources, examples, and workflow profiles through namespaced metadata and resource URIs.

Tools exposed

• tavily.health
• tavily.catalog
• tavily.search
• tavily.extract
• tavily.map
• tavily.crawl
• tavily.research
• tavily.get_research

All tools use typed arguments, tags, annotations, titles, and custom metadata.

MCP client examples

Claude Code project setup

Claude Code can run this package as a local stdio MCP server. Keep the Tavily key in your shell or project secret manager, then add the server:

export TAVILY_API_KEY="tvly-your-key-here"
claude mcp add tavily-fastmcp --scope project \
  --env TAVILY_API_KEY="$TAVILY_API_KEY" \
  -- python -m tavily_fastmcp.server --transport stdio

Useful checks:

claude mcp list
claude mcp get tavily-fastmcp

For a checked-in Claude Code project config, use .mcp.json with environment expansion so secrets stay outside Git:

{
  "mcpServers": {
    "tavily-fastmcp": {
      "type": "stdio",
      "command": "python",
      "args": ["-m", "tavily_fastmcp.server", "--transport", "stdio"],
      "env": {
        "TAVILY_API_KEY": "${TAVILY_API_KEY}"
      }
    }
  }
}

Claude Desktop config snippet

{
  "mcpServers": {
    "tavily-fastmcp": {
      "command": "python",
      "args": ["-m", "tavily_fastmcp.server", "--transport", "stdio"],
      "env": {
        "TAVILY_API_KEY": "tvly-your-key-here"
      }
    }
  }
}

Cursor / Codex style stdio config

{
  "name": "tavily-fastmcp",
  "command": "python",
  "args": ["-m", "tavily_fastmcp.server", "--transport", "stdio"],
  "env": {
    "TAVILY_API_KEY": "tvly-your-key-here"
  }
}

Development

Install everything:

pdm install -G:all

Run the standard checks:

make lint
make type
make test
make docs

Equivalent PDM commands:

pdm run ruff check .
pdm run mypy src
pdm run pytest
pdm run sphinx-build -b html docs/source docs/source/_build/html

Documentation

make docs

The documentation is grouped under:

• docs/source/usage/: MCP, direct Python, and LangChain usage.
• docs/source/guides/: development, automation, and publishing workflows.
• docs/source/reference/: configuration, tools, and profiles.

Publishing

Publishing is intended to run through GitHub Releases and PyPI trusted publishing. Configure the PyPI trusted publisher for repository pr1m8/tavily-fastmcp and workflow file release.yml with environment pypi. If PyPI trusted publishing is not ready yet, add a PyPI API token as the GitHub secret PYPI_API_TOKEN; the release workflow will use it before falling back to OIDC. For the first upload of a brand-new PyPI project, this may need to be an account-scoped token. Rotate it to a project-scoped token after the project exists. Use the local publish gate before tagging:

make publish-check

Then create and push a version tag such as v0.3.1, publish the GitHub Release, and let the Release workflow upload distributions to PyPI. The local make publish target prints the release flow and does not upload packages.

Automation

This project now includes GitHub automation for the full package lifecycle:

• CI runs linting, typing, and tests on pushes and pull requests.
• Docs builds the Sphinx site and uploads the rendered HTML as an artifact.
• Build creates source and wheel distributions and validates them with twine check.
• Release rebuilds the distributions on GitHub Releases and publishes them to PyPI using trusted publishing.
• .readthedocs.yaml configures Read the Docs to build the Sphinx documentation with Python 3.13.