MailPace MCP (Model Context Protocol) サーバーは、MailPace の高速トランザクション メール API を介してメールを送信できるようにする MCP サーバー実装です。
MailPaceトランザクションメール API 経由でメールを送信する
Related MCP server: Postmark MCP Server
1 人以上の受信者に電子メールを送信します。
入力
MailPace ドキュメントに表示されているフィールドを含むメール: https://docs.mailpace.com/reference/send/
Smithery経由で Claude Desktop 用の MailPace MCP Server を自動的にインストールするには:
npx -y @smithery/cli install @mailpace/mailpace-mcp --client claudehttps://app.mailpace.comで組織とドメインを作成します。
ドメインAPIトークンをコピーする
MAILPACE_API_TOKEN環境変数を設定してMCPを起動するか、 --token引数でサーバーに渡します。
npm run build npm run start
MailPace MCPサーバーへの貢献を歓迎します。貢献するには、以下の手順に従ってください。
リポジトリをフォークします。
機能またはバグ修正用の新しいブランチを作成します。
変更をコミットし、ブランチをフォークにプッシュします。
変更の詳細な説明を記載したプル リクエストを作成します。
このプロジェクトはMITライセンスの下でライセンスされています。詳細はLICENSEファイルをご覧ください。
ご質問やサポートについては、 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
