Mailosaur MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILOSAUR_API_KEY | Yes | Your Mailosaur API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mailosaur_messages_getA | Wait for and return the first full message matching criteria. Best for test flows where an email/SMS may arrive shortly. |
| mailosaur_messages_listC | List message summaries for a server. |
| mailosaur_messages_searchC | Search message summaries by sender, recipient, subject, or body. |
| mailosaur_messages_get_by_idB | Retrieve the full detail for a single message by ID. |
| mailosaur_messages_createC | Create a message and optionally send it to a verified external address. |
| mailosaur_messages_forwardC | Forward an email message to a verified address. |
| mailosaur_messages_replyC | Reply to an email message. |
| mailosaur_messages_deleteB | Permanently delete a message and its attachments. |
| mailosaur_messages_delete_allC | Permanently delete all messages and attachments on a server. |
| mailosaur_servers_listA | List all Mailosaur servers. |
| mailosaur_servers_createC | Create a Mailosaur server. |
| mailosaur_servers_getB | Get a Mailosaur server by ID. |
| mailosaur_servers_get_passwordB | Get the SMTP/POP3 password for a Mailosaur server. |
| mailosaur_servers_updateC | Update a Mailosaur server. |
| mailosaur_servers_deleteB | Permanently delete a Mailosaur server and all contained messages. |
| mailosaur_servers_generate_email_addressB | Generate a random email address for a Mailosaur server. |
| mailosaur_files_get_emailC | Download a message as an EML file. Returns base64 content. |
| mailosaur_files_get_attachmentC | Download a message attachment. Returns base64 content. |
| mailosaur_files_get_previewB | Download a generated email preview screenshot. Returns base64 content. |
| mailosaur_analysis_spamC | Run spam analysis for a message. |
| mailosaur_analysis_deliverabilityC | Run deliverability analysis for a message. |
| mailosaur_messages_generate_previewsC | Generate screenshots of an email rendered in selected email clients. |
| mailosaur_previews_list_email_clientsA | List email clients available for generated email previews. |
| mailosaur_devices_listA | List Mailosaur virtual security devices used for TOTP testing. |
| mailosaur_devices_createB | Create a Mailosaur virtual security device from a base32 shared secret. |
| mailosaur_devices_otpB | Retrieve the current TOTP code for a saved device ID or base32 shared secret. |
| mailosaur_devices_deleteC | Permanently delete a Mailosaur virtual security device. |
| mailosaur_usage_limitsB | Retrieve account usage limits. Requires an account-level API key. |
| mailosaur_usage_transactionsB | Retrieve recent transaction usage. Requires an account-level API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Each tool has a distinct resource-action pair clearly indicated by the naming convention, making it easy to differentiate between tools for different purposes.
All tools follow a consistent 'mailosaur_<resource>_<action>' snake_case pattern, providing predictability and ease of understanding.
With 29 tools, the count exceeds the typical well-scoped range (above 25), making the tool set feel heavy and potentially overwhelming for an agent.
The tools comprehensively cover server management, message lifecycle, device handling, file operations, analysis, and usage tracking, leaving no obvious gaps for email testing workflows.