MCP server for Best Temp Mail. 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):

{
  "mcpServers": {
    "best-tempmail": {
      "command": "npx",
      "args": \["-y", "best-tempmail-mcp"]
    }
  }
}

With an API key, for higher limits and verification code extraction:

{
  "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.

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.