zed -tavily

This MCP server is a Zed extension wrapper around the Tavily MCP server. It delegates all MCP protocol handling to the tavily-mcp package, authenticating requests using your Tavily API key. Once configured, the server provides Minecraft MCP-compatible endpoints and behaviors, leveraging Tavily's API-backed query and rate-limited access to Tavily’s data/services. The extension is designed to be plugged into your Zed workspace, enabling you to manage MCP interactions through the Tavily-backed service without implementing the underlying MCP protocol yourself.

To use it, supply your Tavily API key in the server settings (tavily_api_key / TAVILY_API_KEY). The MCP server will then route relevant MCP operations through Tavily’s API, so you can perform queries, lookups, and other supported MCP actions via Tavily’s infrastructure. If you need to adjust usage, review Tavily’s quotas (Free tier offers 1,000 queries/month) and ensure you keep your API key secure. The integration aims to provide a seamless bridge between your Zed environment and Tavily’s MCP capabilities.

Prerequisites:

• Node.js (14.x or newer) and npm/yarn installed
• Access to install NPM packages (npx available)
• Tavily API key for MCP access

Install steps:

1. Ensure Node.js is installed. Verify: node -v npm -v

2. Install the Tavily MCP wrapper via npx (no permanent install required): npx -y tavily-mcp

3. Provide your Tavily API key in the server settings (as per the README): In Zed settings, set: { "context_servers": { "mcp-server-tavily": { "settings": { "tavily_api_key": "YOUR_API_KEY" } } } }

4. Run the MCP server through your usual workflow (the wrapper will initialize with the provided API key). If you manage processes manually, you can instead install the tavily-mcp package locally and invoke the server according to tavily-mcp's own documentation.

Notes and tips:

• This MCP server requires a Tavily API key configured in the settings. Keep your key secure and rotate if needed.
• The Free Tavily tier provides up to 1,000 queries per month; monitor usage to avoid interruptions.
• If you encounter authentication errors, double-check the API key format and ensure it’s correctly exposed to the process running tavily-mcp (environment variable naming is TAVILY_API_KEY).
• If Tavily updates their MCP interface, you may need to update the tavily-mcp package to stay compatible.
• This configuration uses npx to fetch and run tavily-mcp on demand; you can also install tavily-mcp locally and run it via a standard node command if your environment requires a persistent binary.