zed-mcp-server-tavily

Provides an MCP (Model Context Protocol) server wrapper for Tavily, intended to be used as a Zed context server. It requires a Tavily API key for authentication and delegates retrieval/search capabilities to Tavily via the underlying Tavily MCP implementation.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp zed tavily retrieval search rag rust api-key
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
51
/ 100
Is it safe for agents?
⚡ Reliability
30
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
55
Error Messages
0
Auth Simplicity
85
Rate Limits
10

🔒 Security

TLS Enforcement
85
Auth Strength
60
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
45

TLS usage is not explicitly stated in the provided README; most APIs operate over HTTPS, but this cannot be confirmed from the excerpt. Authentication is via a single API key with no documented scopes. Secret handling practices (e.g., logging/headers) are not described; the README only shows storing the key in Zed settings.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
20
AF Security Reliability

Use Cases

  • • RAG and agentic research workflows that need web search or information retrieval via Tavily
  • • Zed-based agent setups that want to call Tavily through MCP tools
  • • Augmenting LLM responses with up-to-date external information

Not For

  • • Use when you cannot provide/manage a Tavily API key
  • • High-assurance environments that require strong guarantees about data handling/compliance (not specified in provided docs)
  • • Workflows requiring guaranteed idempotency semantics from the MCP tool calls (not specified)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: API key (tavily_api_key)
OAuth: No Scopes: No

Authentication is via a Tavily API key passed in Zed settings as `tavily_api_key`. Scope/permission granularity is not described in the provided README.

Pricing

Free tier: Yes
Requires CC: No

Pricing details beyond free tier and query limits are not provided in the README excerpt.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ No tool names, parameters, or error semantics are documented in the provided README; agent integration may require inspecting the underlying `tavily-mcp` project.
  • ⚠ No rate-limit headers/behavior are documented here; agents should be prepared for provider-side throttling without guidance.
  • ⚠ No idempotency or safe-retry guidance is provided for MCP tool calls.

Alternatives

Use Tavily directly via its own API (if available) rather than via MCP Use another MCP server or retrieval tool (e.g., browser/search based MCP integrations) Build a custom MCP wrapper around Tavily’s API with your own error handling and telemetry

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-tavily.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered