用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oyi77/1ai-skills --skill resend-mcp命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | resend-mcp |
| description | Resend Mcp. Use when working with resend mcp in mcp domain. |
| domain | mcp |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | mcp |
| tags | ["mcp","mcp-server","model-context-protocol","resend","tool-integration"] |
| version | 1.0.0 |
Trigger phrases:
Use cases:
When NOT to use:
Resend Mcp implements a Model Context Protocol server for Model Context Protocol.
Resend is a modern email API that provides reliable email delivery for transactional, marketing, and broadcast use cases. It handles domain verification (SPF, DKIM, DMARC), bounce and complaint processing, and delivery analytics out of the box. The Resend MCP server wraps this API into model-context-protocol tools, allowing AI agents to send and track emails as part of autonomous workflows.
The MCP server exposes a send-email tool with typed parameters for recipient, subject, body, and optional configuration (HTML content, attachments, CC/BCC, reply-to headers). Agents can integrate email delivery into their decision loops — sending verification codes, lead follow-ups, alert notifications, or report summaries without leaving the MCP conversation. The server also supports SSE transport for production deployments behind reverse proxies with TLS termination.
pip install resend-sdk mcp
npm install resend @modelcontextprotocol/sdk
# or
pnpm add resend @modelcontextprotocol/sdk
export RESEND_API_KEY="re_xxxxxxxxxxxxx"
Add to your .env file for local development.
send-email action. Specify typed parameters: recipient, subject, body, and optional fields (CC, attachments, HTML content).resend.emails.send() with the validated parameters, and return the result or error to the MCP client.| Rationalization | Reality |
|---|---|
| "I will just use curl" | MCP handles auth, retries, streaming, and type safety. Use the SDK. |
| "One mega-server is simpler" | Single-responsibility servers are easier to debug and maintain. |
| "MCP is just a wrapper" | MCP enables cross-platform tool sharing. It is infrastructure, not overhead. |
| "Resend is just for transactional email" | Resend supports transactional, marketing, and broadcast emails. The MCP server abstracts all of them behind a unified tool interface. |
| "I should build my own email API" | Resend handles deliverability, DKIM, bounce handling, and domain warmup. Building these in-house is weeks of work. |
| "MCP tools are only for text" | MCP tools can integrate full email capabilities — attachments, HTML templates, CC/BCC, reply-to headers, and delivery webhooks. |
// Example: MCP server tool definition
import { McpServer } from "@modelcontextprotocol/sdk";
const server = new McpServer({ name: "my-tools", version: "1.0.0" });
server.tool("search", { query: z.string() }, async ({ query }) => {
const results = await search(query);
return { content: [{ type: "text", text: JSON.stringify(results) }] };
});
import os
from resend import Resend
resend = Resend(api_key=os.environ["RESEND_API_KEY"])
r = resend.emails.send({
"from": "onboarding@resend.dev", # Use your verified domain in production
"to": ["user@example.com"],
"subject": "Hello from Resend MCP",
"text": "This email was sent through the Resend API.",
})
print(f"Email sent: {r['id']}")
import { Resend } from 'resend';
const resend = new Resend(process.env.RESEND_API_KEY);
const { data, error } = await resend.emails.send({
from: 'onboarding@resend.dev',
to: ['user@example.com'],
subject: 'Hello from Resend MCP',
text: 'This email was sent through the Resend API.',
});
if (error) {
console.error('Send failed:', error);
} else {
console.log('Email sent:', data.id);
}
import { McpServer } from "@modelcontextprotocol/sdk";
import { z } from "zod";
import { Resend } from "resend";
const resend = new Resend(process.env.RESEND_API_KEY);
const server = new McpServer({ name: "email-tools", version: "1.0.0" });
server.tool(
"send-email",
{
to: z.string().describe("Recipient email address"),
subject: z.string().describe("Email subject line"),
text: z.string().describe("Email body text"),
},
async ({ to, subject, text }) => {
const { data, error } = await resend.emails.send({
from: "noreply@yourdomain.com",
to: [to],
subject,
text,
});
if (error) return { content: [{ type: "text", text: }] };
{ : [{ : , : }] };
}
);
| Problem | Solution |
|---|---|
| "Resend API key not recognized" | Verify RESEND_API_KEY is set in environment and the key is active in the Resend dashboard. Keys start with re_. |
| "MCP tool returns empty response" | Ensure the transport (stdio/SSE) is properly configured on both server and client sides. Check for port conflicts. |
| "Email delivery delayed or dropped" | Confirm sender domain is verified in Resend. SPF, DKIM, and DMARC records must be configured for the sending domain. |
| "Rate limit exceeded (429)" | Resend defaults to 5 req/s on free tier. Implement exponential backoff retry logic in your MCP tool handler. |
| "Connection refused on SSE transport" | The MCP server process may not be running. Verify the process is alive and listening on the configured port. Use `ps aux |
| "TypeError in tool schema validation" | Ensure all JSON Schema definitions in your tool parameters match the actual types sent. Use zod for TypeScript or pydantic for Python schema validation. |