Skip to main content
AgentsUse

Search and Retrieval APIs

Use Tavily with Microsoft Agent Framework

The recorded connection between Tavily and Microsoft Agent Framework is Connected through MCP (Agent Framework MCP client connected to the official Tavily MCP server (tavily-mcp)). This page records the connection and links the evidence behind it.

Connected through MCPChecked 2026-10-29Source-verified

This page is published for readers and kept out of the search index until the pairing carries a configuration example checked against the source.

Pairing facts

Connection type
Connected through MCP
Package or path
Agent Framework MCP client connected to the official Tavily MCP server (tavily-mcp)
Tool job
Search and Retrieval APIs
Tool review state
Source-verified. Checked 2026-10-29.

Why this pairing

A web access API built for AI agents: search, extract, map, crawl, and research endpoints behind one key.

Best for: Agents that need current web facts with cited results, research workflows that combine search with page extraction, and teams that want one vendor for search and fetching.

Not ideal for: Fully offline or self-hosted stacks, and high-volume crawling without a credit budget.

Evidence

The Microsoft Learn overview lists MCP clients among the framework's foundational building blocks and states agents call tools and MCP servers. Tavily publishes an official MCP server, catalogued on AgentsUse at /mcp/tavily, so the pairing runs over MCP rather than a Tavily-specific adapter.

https://learn.microsoft.com/en-us/agent-framework/overview/

Scope

Compatibility means the cited page documents the pairing. It does not mean AgentsUse benchmarked the combination or that every version behaves the same. Pin versions, start with a small job, and review the first outputs before widening access.

Watch for

  • Metered by credits, so unattended crawl loops need spending controls.
  • A managed service: no self-hosted fallback when Tavily is down or a source blocks it.

Keep reading