tempmail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMPMAIL_API_KEY | Yes | Your key for the tempmail API. | |
| TEMPMAIL_BASE_URL | No | Only for self-hosted installs. | https://tempmailgenerator.net |
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_mailboxA | Create a temporary email address. Returns the address to paste into a signup form and the id used by the other tools. Without arguments you get a random name on a random domain, which is what you usually want. |
| wait_for_codeA | Wait for an email to arrive and return the confirmation code and activation link extracted from it. Call this right after triggering the signup. It blocks until the message lands, so there is no need to poll or to sleep between calls. |
| list_messagesA | List what has arrived in a mailbox, newest first, with a short preview of each. Use it when the code extraction found nothing and you need to look at the mail yourself. |
| read_messageA | Return the full body of one message, plain text where available. Use it when the preview is not enough or when the code sits in an unusual place. |
| delete_mailboxA | Delete the mailbox and everything in it once you are done. Not required, since mailboxes expire on their own in 24 hours, but polite and it frees your quota. |
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 5 tools
Each tool has a clearly distinct role: create_mailbox sets up the address, wait_for_code extracts codes, list_messages and read_message offer progressively deeper inspection, and delete_mailbox cleans up. There is no overlap or ambiguity between the operations.
All tool names follow a consistent verb_noun pattern in snake_case: create_mailbox, wait_for_code, list_messages, read_message, delete_mailbox. The naming style is uniform and predictable throughout the set.
Five tools is a well-scoped size for a temporary email server. Each tool covers an essential step in the workflow without redundancy or unnecessary additions.
The tools cover the full temporary email lifecycle: create a mailbox, wait for and extract a code, list and read messages for manual inspection, and optionally delete the mailbox. There are no obvious dead ends or missing operations for the stated purpose.