zed-resend-mcp-server

Provides a Zed context-server/MCP integration that sends emails through Resend using the (unofficial) resend-mcp npm package. Configuration is done via Zed settings.json with a Resend API key and optional sender/reply-to and related email fields (recipients, CC/BCC, scheduling, and attachments, plus remote URL attachments).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Communication email mcp zed-extension resend automation messaging

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README indicates API key is configured via Zed settings.json. Scope granularity and operational security practices (logging redaction, key rotation, least-privilege, idempotency) are not documented. The integration relies on an unofficial third-party npm package, increasing supply-chain/maintenance risk.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an MCP-enabled email-sending capability inside Zed for transactional use cases and are comfortable using a third-party/unofficial resend-mcp dependency.

Avoid When

You need React Email templates or email tracking, or you require a formally documented, first-party MCP implementation with strong guarantees around API behavior and error handling.

Use Cases

• Send transactional emails from within the Zed assistant workflow
• Trigger email sending with generated content (plain text and/or HTML)
• Automate scheduling of outbound emails
• Send emails with attachments (file and remote URL)

Not For

• Email marketing/batch campaigns (explicitly marked as not supported: batch sending)
• React Email template workflows (explicitly not supported)
• Workflows requiring email open/click tracking (explicitly not supported)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: resend_api_key

OAuth: No Scopes: No

Authentication is via Resend API key provided in Zed settings.json. No OAuth flow or scoped-granular auth is described in the README.

Pricing

Free tier: No

Requires CC: No

Pricing for the MCP server extension itself is not described; Resend pricing would apply for email delivery.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Email sending is typically non-idempotent: agents retrying requests may cause duplicate emails unless the integration explicitly supports idempotency (not documented here).
⚠ Some features are explicitly not supported (React Email templates, batch sending, email tracking).
⚠ Attachment support includes remote URL attachments; ensure the URLs and content are safe and accessible to the server.

Alternatives

Use Resend directly via your own API client from Zed (if Zed supports generic HTTP tools) Adopt an official/first-party Resend integration (if available) rather than an unofficial resend-mcp bridge Build a small custom MCP server that calls Resend's HTTP API directly

Full Evaluation Report

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

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

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.