best-tempmail-mcp
# best-tempmail-mcp
MCP server for [Best Temp Mail](https://best-tempmail.com/api). Gives an AI assistant its own disposable email inboxes, so it can sign up for things, wait for the mail, and read the verification code back to you.
> "Create a temp email, sign me up for that newsletter, and tell me the confirmation code."
## Install
Add this to your MCP host's configuration. No installation step: `npx` fetches it on first run.
**Claude Desktop** (`claude\_desktop\_config.json`):
```json
{
"mcpServers": {
"best-tempmail": {
"command": "npx",
"args": \["-y", "best-tempmail-mcp"]
}
}
}
```
**With an API key**, for higher limits and verification code extraction:
```json
{
"mcpServers": {
"best-tempmail": {
"command": "npx",
"args": \["-y", "best-tempmail-mcp"],
"env": { "BTM\_API\_KEY": "btm\_sk\_live\_..." }
}
}
}
```
The same shape works in Cursor, VS Code, Claude Code, and other MCP hosts.
Restart the host after editing the config.
## Tools
|Tool|What it does|
|-|-|
|`create\_inbox`|Create a disposable address|
|`wait\_for\_email`|Wait up to 55s for mail to arrive|
|`get\_verification\_code`|Pull the OTP out of a message (paid key)|
|`list\_messages`|See what has already arrived|
|`read\_message`|Read the full body and attachment list|
|`list\_domains`|Available domains|
|`delete\_inbox`|Delete an inbox and its contents|
## Without an API key
Everything works except `get\_verification\_code`, on the free tier: 150 requests per hour and 3 inboxes per day. That is enough to try it properly.
A paid key raises the limit to 2,000 requests per hour, unlocks code extraction, and allows commercial use. See [pricing](https://best-tempmail.com/api/pricing).
## What it looks like in use
> \*\*You:\*\* Make me a temp email and sign up for the newsletter at example.com
>
> The assistant calls `create\_inbox`, gets `abc1234@dextde.site`, fills in the form, then calls `wait\_for\_email`.
>
> \*\*Assistant:\*\* Signed up with abc1234@dextde.site. The confirmation email arrived; your code is 889231.
## Configuration
|Variable|Purpose|
|-|-|
|`BTM\_API\_KEY`|Optional. Paid plan key.|
|`BTM\_BASE\_URL`|Optional. Override the API base, for testing.|
## Notes
Inboxes expire on their own: 2 hours on the free and Developer plans, 24 hours on Pro. They are receive-only, so nothing can be sent from them.
If a verification code cannot be identified with confidence, the tool says so rather than guessing. A wrong code is worse than none, and the assistant can fall back to `read\_message` to look at the body itself.
## Links
* [API documentation](https://best-tempmail.com/api)
* [Node SDK](https://www.npmjs.com/package/best-tempmail)
* [Python SDK](https://pypi.org/project/best-tempmail/)
## License
MIT
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.