Best Tempmail Mcp

io.github.mbilalawan926-sysPublished by GitHub account mbilalawan926-sysv1.0.2Updated Oct 24, 2026

Disposable email inboxes for AI agents: create, wait for mail, extract verification codes

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that gives an AI assistant disposable email inboxes so it can sign up for services, wait for mail, and read verification codes.

What you can do
Create and delete disposable inboxes, and list available domains to pick an address from. Wait for incoming mail and list messages that have already arrived. Read a message's full body and attachment list. Extract a verification code from a message, which requires a paid API key.
When to use it
Useful when an assistant needs a throwaway address to complete a sign-up, newsletter, or confirmation flow and report the code back. Also handy for testing email-driven workflows without using a real personal inbox.
Requirements
Runs locally as a Node.js process, fetched on first run with npx; no separate install step. No account is required for the free tier. An optional paid plan key is supplied through the BTM_API_KEY environment variable. Network access to the Best Temp Mail API is needed.
Before you install
The paid key is a secret passed in BTM_API_KEY; keep it out of shared configs. The free tier is limited to 150 requests per hour and 3 inboxes per day, and cannot extract verification codes. Inboxes are receive-only and expire on their own (2 hours on free and Developer plans, 24 hours on Pro). Creating and deleting inboxes changes state on a third-party service, and message contents are read from that service.

Installation

In SourceWeft

  1. Open Best Tempmail Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

best-tempmail-mcp

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):

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

ToolWhat it does
create\_inboxCreate a disposable address
wait\_for\_emailWait up to 55s for mail to arrive
get\_verification\_codePull the OTP out of a message (paid key)
list\_messagesSee what has already arrived
read\_messageRead the full body and attachment list
list\_domainsAvailable domains
delete\_inboxDelete 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 [email protected], fills in the form, then calls wait\_for\_email.

**Assistant:** Signed up with [email protected]. The confirmation email arrived; your code is 889231.

Configuration

VariablePurpose
BTM\_API\_KEYOptional. Paid plan key.
BTM\_BASE\_URLOptional. 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

License

MIT

Source: README.md at commit 9851207

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts