best-tempmail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BTM_API_KEY | No | Optional. Paid plan key. | |
| BTM_BASE_URL | No | Optional. Override the API base, for testing. |
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_inboxA | Create a temporary email address that can receive mail. Use this when the user needs an email address for a signup, a trial, or anything they do not want to give a real address to. Returns the address and when it expires. |
| wait_for_emailA | Wait for the next email to arrive at an inbox, up to 55 seconds. Use this straight after triggering a signup or password reset. Returns the message summary, or reports that nothing arrived. Nothing arriving is not an error: the mail may simply be slow, and calling this again continues waiting. |
| get_verification_codeA | Pull the verification or one-time code out of a message. Use this after wait_for_email when the user needs a code to complete a signup or login. Requires a paid API key. If no code is found with confidence, that is reported rather than guessed, because a wrong code is worse than none. |
| list_messagesA | List the messages currently in an inbox, newest first. Use this to see what has already arrived, rather than waiting for something new. |
| read_messageA | Read a message's full body and attachment list. Use this when the user wants to see what an email actually says, or when get_verification_code could not find a code. |
| list_domainsA | List the domains inboxes can be created on. Only needed when the user wants a specific domain; create_inbox picks one automatically. |
| delete_inboxA | Delete an inbox and everything in it. Inboxes expire on their own, so this is only needed when the user wants it gone immediately. |
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 7 tools
Each tool targets a distinct stage of the temporary-email workflow: create inbox, list mail, wait for mail, read a message, extract a code, list domains, and delete inbox. Close pairs like list_messages/wait_for_email and read_message/get_verification_code are explicitly differentiated in their descriptions.
All tool names use a consistent snake_case, verb-first convention: create_inbox, list_messages, read_message, delete_inbox, wait_for_email, and get_verification_code. The phrasal wait_for_email still fits the predictable pattern.
Seven tools provide a well-scoped set for a focused temporary-email server. Each tool has a clear role and none feels redundant, while the count stays comfortably within the ideal range.
The surface covers the full temporary-email lifecycle: create an inbox, optionally choose a domain, wait for or list incoming messages, read message content, extract verification codes, and delete the inbox. No significant workflow gap is apparent for a receive-only temp-email service.