Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MailPace MCP Server send a welcome email to newuser@example.com with subject 'Welcome!' and body 'Thanks for signing up!'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MailPace MCP (Model Context Protocol) Server is an MCP server implementation that allows sending emails over MailPace's fast transactional email API.
Send email over the MailPace Transactional Email API
Related MCP server: Postmark MCP Server
Sends an email to one or more recipients.
Inputs
Email with fields shown in MailPace documentation: https://docs.mailpace.com/reference/send/
To install MailPace MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @mailpace/mailpace-mcp --client claudeCreate an organization and domain at https://app.mailpace.com
Copy your domain API token
Start the MCP with the MAILPACE_API_TOKEN env set, or pass it to the server with the --token argument
npm run build
npm run start
We welcome contributions to the MailPace MCP Server. To contribute, please follow these steps:
Fork the repository.
Create a new branch for your feature or bugfix.
Commit your changes and push the branch to your fork.
Create a pull request with a detailed description of your changes.
This project is licensed under the MIT License. See the LICENSE file for more details.
For any questions or support, please contact us at 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. Dates show when Glama detected each change.
v1.0.0send-emailWith 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for MailTempo's public free temporary email inboxes.
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mailpace/mailpace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
