{"id":"resend-resend-mcp","name":"resend-mcp","af_score":61.8,"security_score":48.2,"reliability_score":38.8,"what_it_does":"Provides an MCP server for the Resend email platform, enabling MCP clients to send/receive and manage related email resources (contacts, broadcasts, domains, segments, topics, API keys, and webhooks) via stdio (default) or HTTP transport.","best_when":"You want to integrate Resend capabilities into an AI agent workflow through MCP (Claude Desktop/Cursor/Claude Code), either locally over stdio or via HTTP.","avoid_when":"You need fine-grained organizational access controls beyond what a single Resend API key can provide, or you want to avoid passing credentials to an HTTP MCP endpoint.","last_evaluated":"2026-03-30T13:27:36.811931+00:00","has_mcp":true,"has_api":false,"auth_methods":["Resend API key for stdio mode (RESEND_API_KEY)","Bearer token via Authorization header for HTTP mode"],"has_free_tier":false,"known_gotchas":["HTTP transport requires clients to pass Authorization: Bearer <Resend API key>; ensure you don’t expose the key or send it to untrusted environments.","If SENDER_EMAIL_ADDRESS is not provided, the server may prompt/ask for a sender on each call (per README note), which can disrupt fully automated flows.","Idempotency behavior for send/cancel/update operations is not documented in the README; agents may need to avoid automatic retries without confirmation."],"error_quality":0.0}