MailPace MCP（模型上下文协议）服务器是一种 MCP 服务器实现，允许通过 MailPace 的快速事务电子邮件 API 发送电子邮件。
通过MailPace交易电子邮件 API 发送电子邮件
Related MCP server: Postmark MCP Server
向一个或多个收件人发送电子邮件。
输入
MailPace 文档中显示的字段的电子邮件： https://docs.mailpace.com/reference/send/
要通过Smithery自动为 Claude Desktop 安装 MailPace MCP 服务器：
npx -y @smithery/cli install @mailpace/mailpace-mcp --client claude在https://app.mailpace.com创建组织和域
复制您的域 API 令牌
使用MAILPACE_API_TOKEN环境设置启动 MCP，或使用--token参数将其传递给服务器
npm run build npm run start
欢迎为 MailPace MCP 服务器做出贡献。请按以下步骤操作：
分叉存储库。
为您的功能或错误修复创建一个新的分支。
提交您的更改并将分支推送到您的 fork。
创建一个拉取请求，其中包含更改的详细描述。
本项目遵循 MIT 许可证。更多详情请参阅许可证文件。
如有任何疑问或需要支持，请联系我们： support@mailpace.com
| Name | Required | Description | Default |
|---|---|---|---|
| attachments | No | ||
| bcc | No | ||
| cc | No | ||
| from | Yes | ||
| htmlbody | No | ||
| inreplyto | No | ||
| list_unsubscribe | No | ||
| references | No | ||
| replyto | No | ||
| subject | No | ||
| tags | No | ||
| textbody | No | ||
| to | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0send-emailScored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool 'send-email' has a clear and distinct purpose without any ambiguity.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'send-email' follows a verb-noun structure and stands alone without deviation.
A single tool for an email server is too minimal for the apparent scope, as email management typically involves more operations like listing, deleting, or managing templates. This feels thin and incomplete for the domain.
The tool surface is severely incomplete for an email server, covering only sending emails with no support for other essential operations like retrieving sent emails, managing contacts, or handling attachments. This will cause significant agent failures in email-related workflows.
MCP server for MailTempo's public free temporary email inboxes.
Shipmail MCP server. Modern email for your business, with an API for your agents.
An MCP server that provides email capabilities, hosted on Alpic platform
