MailPace MCP(Model Context Protocol) 서버는 MailPace의 빠른 트랜잭션 이메일 API를 통해 이메일을 보낼 수 있는 MCP 서버 구현입니다.
MailPace Transactional Email API를 통해 이메일 보내기
Related MCP server: Postmark MCP Server
한 명 이상의 수신자에게 이메일을 보냅니다.
입력
MailPace 문서에 표시된 필드가 있는 이메일: https://docs.mailpace.com/reference/send/
Smithery를 통해 Claude Desktop용 MailPace MCP 서버를 자동으로 설치하려면:
지엑스피1
https://app.mailpace.com 에서 조직과 도메인을 만드세요
도메인 API 토큰을 복사하세요
MAILPACE_API_TOKEN 환경 설정으로 MCP를 시작하거나 --token 인수로 서버에 전달합니다.
npm run build npm run start
MailPace MCP 서버에 대한 여러분의 기여를 환영합니다. 기여하려면 다음 단계를 따르세요.
저장소를 포크합니다.
기능이나 버그 수정을 위해 새로운 브랜치를 만듭니다.
변경 사항을 커밋하고 포크에 브랜치를 푸시합니다.
변경 사항에 대한 자세한 설명과 함께 풀 리퀘스트를 생성하세요.
이 프로젝트는 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
