tavily-firecrawl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | Yes | Tavily API key for web search and extraction | |
| WEB_FETCH_PROXY | No | Optional proxy URL for outbound requests | |
| FIRECRAWL_API_KEY | No | Optional Firecrawl API key for fallback web fetching |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_fetchA | Fetch and extract the content of a web page as markdown (or plain text). Tries Tavily first; on failure or empty result, automatically falls back to Firecrawl. Requires TAVILY_API_KEY and/or FIRECRAWL_API_KEY in the server's environment. |
| web_searchA | Search the web with Tavily and return titles, URLs, and snippets (plus an optional synthesized answer). No fallback — requires TAVILY_API_KEY in the server's environment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
web_fetch extracts page content as markdown, while web_search returns search results with titles and snippets. Their purposes are clearly distinct with no overlap.
Both tools follow a consistent verb_noun pattern using snake_case (web_fetch, web_search), making the naming predictable and clear.
With only 2 tools, the server feels minimal. While it covers the core operations of searching and fetching, the count is low for a combined service, though still functional.
The basic lifecycle of web content retrieval (search and fetch) is covered. Minor gaps include lack of explicit service selection or advanced options like pagination, but the main use cases are handled.