Mailsac MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILSAC_DOMAIN | No | Domain for new test addresses. Set it to your private domain. | mailsac.com |
| MAILSAC_API_KEY | Yes | Your Mailsac API key | |
| MAILSAC_API_URL | No | API base URL | https://mailsac.com/api |
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 |
|---|---|
| create_test_addressA | Return a new, unique address that can receive email immediately, with nothing to set up. Use one address per test so tests never read each other's mail. Makes no API call. |
| wait_for_emailA | Poll an address until a matching email arrives, then return its subject, sender, text, links, the most likely confirm/reset/login link (actionLink) and candidate one-time codes. Each poll uses one Mailsac operation. |
| list_emailsA | List the emails currently stored for an address, newest first (no bodies). One operation. |
| read_emailB | Read one email. format "text" (default) also returns links, actionLink and codes; "html" returns the HTML body; "raw" the full MIME source; "headers" the parsed headers. |
| delete_emailsA | Delete one email (messageId) or every email at an address (omit messageId). Clean up after a test. |
| list_domainsA | List the private domains on this Mailsac account. Mail to a private domain is visible only to the account; pass one as |
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 6 tools
Most tools have clearly distinct purposes (create address, list, read, delete, list domains). wait_for_email overlaps somewhat with list_emails/read_email since all retrieve mail, but the descriptions clarify that wait polls for arrival while the others inspect existing mail.
All six tools follow a clean snake_case verb_noun pattern (create_test_address, wait_for_email, list_emails, read_email, delete_emails, list_domains). Naming is fully predictable.
Six tightly scoped tools are ideal for a test-email service, each mapping to a distinct step in the inbox testing lifecycle. Nothing feels redundant or missing count-wise.
Covers the full receiving workflow: mint an address, await mail, list/read messages, delete for cleanup, and discover private domains. Outbound sending and message search aren't covered, but these are minor for a receive-focused testing tool.