[Benchmark] Tavily 2-step Research is a marketing workflow that chains Tavily to automate a common task. Internal benchmark-only recipe: Tavily search + answer for a topic, 2 tool calls. Once configured, it saves n/a and runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.
Internal benchmark-only recipe: Tavily search + answer for a topic, 2 tool calls.
Execute this recipe in your browser — no local install, no Claude Code. Streams results live.
Benchmark only — 2-step happy-path for APC.
N/A
N/A
Concrete ROI — not marketing fluff.
Time saved
n/a
Tavily
Tavily MCP Server
This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.
You are a research agent. Given a topic: 1. Call tavily.tavily-search with query=<topic> and max_results=3 2. Pick the most relevant URL from step 1 3. Call tavily.tavily-extract with urls=[that_url] 4. Respond with a 3-sentence summary combining both calls. Do not call any other tool.
How this workflow fires and what env vars you need.
Install everything — MCPs, prompt, env template — in a single call.
$ mcpizy recipe install bench-tavily-research-2 ✓ Installs all 1 MCP server ✓ Writes prompt to ~/.mcpizy/prompts/bench-tavily-research-2.md ✓ Generates .env.example in current directory ✓ Ready to paste into Claude Code
Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.
$ n/aRun daily Perplexity searches on competitors and log product updates, pricing changes, and news to a Notion tracker.
Scrape Product Hunt daily with Firecrawl and send trending posts in your category to Slack so your team never misses a launch.
Internal benchmark-only recipe: one Tavily search call, returns a short summary. Not intended for production use.
Internal benchmark-only recipe: 3 Tavily searches on different angles of a topic, then synthesise.
[Benchmark] Tavily 2-step Research is a marketing automation that uses Tavily together via the Model Context Protocol. Internal benchmark-only recipe: Tavily search + answer for a topic, 2 tool calls.
Setup takes around 10-30s per run. You install the required MCP servers with `n/a`, connect your accounts, and the workflow is ready to run.
Once running, this workflow saves n/a. The concrete business value: Benchmark only.
You need 1 MCP server: Tavily (mcpizy install tavily). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.
Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.
Install the required MCPs from the marketplace and automate this in 10-30s per run.
$ n/a
Free to install. Connect your accounts and this workflow runs itself.