zed-resend

This MCP server extension enables Zed to send emails via the Resend service using the unofficial resend-mcp package. It exposes email sending capabilities such as plain text and HTML bodies, support for multiple recipients, CC and BCC, reply-to addresses, scheduled sending, and attaching files or remote URL attachments. You configure the server by providing your Resend API key in Zed's context_servers settings, and optionally a verified sender email address and reply-to addresses. Once configured, you can craft email tasks in Zed that leverage the Resend MCP endpoints to dispatch messages through your Resend account. The server is designed to act as a bridge between Zed’s MCP workflow and Resend’s API, enabling streamlined email campaigns and notifications directly from your workflows.

Usage basics: install and run the MCP server via the chosen runner (npx in this setup). In Zed, add a context_server named mcp-server-resend and supply the required settings, including resend_api_key and optional sender_email_address and reply_to_email_addresses. When sending an email, specify recipients, subject, body (text or HTML), attachments (local or remote URLs), and any scheduling details. The server will route the request to Resend and return the delivery result back to Zed for handling in your automation flow.

Prerequisites:

• Node.js (recommended latest LTS) and npm installed on the machine running the MCP server
• Access to a Resend API key (from your Resend dashboard)

Installation steps:

1. Ensure Node.js and npm are installed
   • node -v
   • npm -v
2. Verify you can use npx (comes with npm)
3. Configure the MCP server in Zed with the Resend API key and optional settings (see Complete Configuration in README).

Optional, if you want to preload the package locally (not required with npx): 4) Install the package globally or in a project (alternative to npx):

• npm install -g resend-mcp
• or npm install --save resend-mcp

5. Start the MCP integration by ensuring Zed can reach the running MCP server according to your environment (local, container, or VM).

Notes and tips:

• Ensure the sender_email_address, if provided, belongs to a verified domain in Resend to avoid delivery failures.
• You can specify reply_to_email_addresses as a comma-separated list; ensure each address is valid.
• The MCP supports scheduling; use the appropriate scheduling fields in your request if you need delayed sending.
• Environment-based configuration is supported; consider exposing the Resend API key as an environment variable for security (e.g., RESEND_API_KEY) and mapping it in your MCP settings.
• Attachments can be local or remote URLs; ensure the server has access to fetch remote attachments where required.
• Some advanced features (e.g., detailed delivery tracking) may be limited by the Resend MCP capabilities; verify feature support in the Resend MCP docs.
• If you encounter authentication or rate-limit errors, double-check the API key scope and domain sender restrictions in your Resend account.