ILoveTempMail
Pro Feature · MCP

Give your AI assistant a disposable inbox

The ILoveTempMail MCP server connects temporary email to Claude, OpenAI Codex, and Cursor. Your assistant can create a throwaway address, wait for the message to arrive, and read the verification code itself — turning “check your email” from a manual chore into one more step the agent handles on its own.

What is the MCP server?

MCP — the Model Context Protocol — is an open standard for giving AI tools access to live data and actions. Instead of being limited to what it was trained on, an MCP-connected assistant can call real tools you authorize.

ILoveTempMail exposes a remote (Streamable HTTP) MCP server. You add one URL, authenticate with a personal access token, and your assistant gains a small, focused set of temp-mail tools — all scoped to your account. It never sees your password and can only touch mailboxes created under your token.

Why connect temp mail to your assistant?

Automated sign-up & verification

Ask your assistant to register for a service end to end — it creates the address, fills the form, waits for the email, and reads the confirmation code back to you. No copy-pasting between tabs.

Testing email flows

Developers and QA can have an agent create dozens of throwaway inboxes to exercise welcome emails, password resets, and OTP delivery while building or debugging.

Keeping your real inbox clean

Trial a tool or grab a one-time download link without handing over your primary email. The disposable mailbox auto-expires, so there is nothing to unsubscribe from later.

Agent workflows that need a code

Any multi-step task your agent runs that hits an email verification wall can now get past it on its own, instead of stopping to ask you for the code.

What it can do

The server ships seven tools. Your assistant decides which to call based on what you ask — you just talk to it in plain language.

create_temp_email

Spin up a fresh disposable address (standard or premium domain) with an optional label and expiry.

list_mailboxes

Browse the mailboxes your assistant has created, newest first, with simple pagination.

search_mailbox

Find a specific mailbox by address or label when you have a lot of them in flight.

list_messages

Poll an inbox for incoming mail — senders, subjects and timestamps — so the agent knows when a code has landed.

get_message

Read the full subject, plain-text and HTML body of a message. The agent extracts any OTP or link itself.

delete_mailbox

Clean up a disposable address once it has done its job.

get_usage

Check this month's remaining mailbox and tool-call quota. This call is always free.

Note: ILoveTempMail does not parse OTP or verification codes on the server. Messages are returned raw so your assistant reads whatever code or link it needs directly — nothing about your emails is interpreted server-side.

Before you start

  1. 1
    Make sure you have ILoveTempMail Pro. Subscribe in the iOS or Android app; premium syncs to web automatically.
  2. 2
    Generate an access token on the MCP Server page. Copy it immediately — it is shown only once.
  3. 3
    Keep these two values handy for every setup below:
    Server URL
    https://api.ilovetempmail.com/v2/mcp
    Auth header
    Authorization: Bearer YOUR_TOKEN

Connect Claude

Claude Code speaks remote HTTP MCP natively. Run this in your terminal, swapping in your token:

claude mcp add --transport http ilovetempmail https://api.ilovetempmail.com/v2/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Claude Desktop uses a config file (Settings → Developer → Edit Config). Add the server through themcp-remote bridge:

claude_desktop_config.json
{
  "mcpServers": {
    "ilovetempmail": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.ilovetempmail.com/v2/mcp",
        "--header",
        "Authorization: Bearer YOUR_TOKEN"
      ]
    }
  }
}

Restart Claude Desktop afterwards. You should see the ILoveTempMail tools appear in the tools menu.

Connect OpenAI Codex

Codex reads MCP servers from ~/.codex/config.toml. Add an entry that launches the mcp-remote bridge so the remote server works with Codex's stdio transport:

~/.codex/config.toml
[mcp_servers.ilovetempmail]
command = "npx"
args = [
  "-y",
  "mcp-remote",
  "https://api.ilovetempmail.com/v2/mcp",
  "--header",
  "Authorization: Bearer YOUR_TOKEN"
]

Start a new Codex session and ask it to list its tools to confirm the connection.

Connect Cursor

Cursor supports remote MCP servers directly. Add the server to your project (.cursor/mcp.json) or globally (~/.cursor/mcp.json):

.cursor/mcp.json
{
  "mcpServers": {
    "ilovetempmail": {
      "url": "https://api.ilovetempmail.com/v2/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Open Cursor Settings → MCP to verify the server shows a green “connected” status, then enable it for your chats.

Try it: example prompts

Once connected, just ask in natural language. For example:

“Create a temp email, sign me up for this newsletter, and tell me the confirmation code when it arrives.”
“Make 3 disposable inboxes for testing and list their addresses.”
“Check my latest temp inbox and read me the verification code from the most recent email.”
“How much of my monthly MCP quota have I used this month?”

Good to know

Scoped & revocable

Each token only accesses mailboxes created under your account. Lost a token or done testing? Revoke it on the MCP Server page and any tool using it loses access instantly. Only one token is active at a time.

Monthly quotas

Usage is metered per month — mailbox creations and tool calls each have a generous cap that resets at the start of the month. Ask the assistant to run get_usage any time to see what's left; that check never counts against your quota.

Keep your token secret

Treat the token like a password. Store it in your tool's config, not in shared chats or committed files.

Ready to connect?

Generate your access token and paste the server URL into Claude, Codex, or Cursor.

Go to the MCP Server page