Skip to main content

tmailor-mcp

MCP server for the Tmailor Open API. It gives AI agents (Claude, Cursor, VS Code Copilot and any other MCP client) real, receive-only temporary email addresses: sign up somewhere, wait for the email, get the one-time code or the verification link.

You:   Sign up on example.com with a temporary email and confirm the account.
Agent: create_mailbox -> k3x9q2m7@picdirect.net
       (fills in the sign-up form)
       wait_for_message -> otp "482913", links ["https://example.com/confirm?t=..."]

Billing counts mailboxes, not requests: creating an address uses 1 unit of quota, while waiting for and reading mail is free. Addresses never expire.

Requirements

  • A Tmailor API key: sign in at https://platform.tmailor.com and create one under API keys.
  • uv (for uvx) or Python 3.10+.
  • On the Free plan the API only accepts calls from your allowlisted IP: add the public IP of the computer that runs the MCP server under IP allowlist. Paid plans accept calls from any IP.

Install

The server runs locally over stdio. The API key is read from the TMAILOR_API_KEY environment variable.

Claude Code

claude mcp add tmailor -e TMAILOR_API_KEY=tmk_live_... -- uvx tmailor-mcp

Claude Desktop

Edit claude_desktop_config.json (Settings > Developer > Edit Config):

{
  "mcpServers": {
    "tmailor": {
      "command": "uvx",
      "args": ["tmailor-mcp"],
      "env": { "TMAILOR_API_KEY": "tmk_live_..." }
    }
  }
}

Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project) uses the same mcpServers block as above.

VS Code

.vscode/mcp.json. The key is asked once and stored by VS Code instead of being written in the file:

{
  "inputs": [
    { "type": "promptString", "id": "tmailor-key", "description": "Tmailor API key", "password": true }
  ],
  "servers": {
    "tmailor": {
      "type": "stdio",
      "command": "uvx",
      "args": ["tmailor-mcp"],
      "env": { "TMAILOR_API_KEY": "${input:tmailor-key}" }
    }
  }
}

Other MCP clients

tmailor-mcp is listed in the MCP Registry as io.github.tmailor-com/tmailor-mcp, so clients that browse the registry can install it directly.

Without uv

pip install tmailor-mcp
TMAILOR_API_KEY=tmk_live_... tmailor-mcp

Tools

Tool What it does
create_mailbox Create an address (random on a shared domain, or a chosen name on your own verified domain). Uses 1 quota unit.
wait_for_message Return the newest unread message matching optional sender/subject filters, or wait for one (up to 300 s). Includes otp, codes, links and the text.
list_messages Messages of an address (last 24 hours), without body.
read_message One message with otp, codes, links and text.
delete_mailbox Delete an address for good. Quota is not returned.
list_mailboxes Your addresses, newest first.
list_domains Your own domains and whether shared domains are available.
account_status Remaining quota, plans, request rate.

Tools take and return email addresses only. The address tokens of the API stay inside the server process, so they never end up in the conversation.

Security notes

  • Email content is untrusted. Anyone can send mail to an address. The server returns plain text only (no HTML), cuts it to max_chars, and marks every message with untrusted_content_notice. Agents should use mail as data (codes, links) and never follow instructions written inside it.
  • Keep the key out of shared files. Prefer the VS Code inputs prompt, or a user-level config file that is not committed to a repository. Revoke a leaked key at https://platform.tmailor.com/keys.
  • Paid plans accept API calls from any IP, so a leaked key can be used from anywhere until you revoke it.
  • wait_for_message never returns the same message twice within one server process. Two MCP servers waiting on the same address at the same time (for example two agents sharing one key) can both receive the same message.

Configuration

Variable Meaning
TMAILOR_API_KEY Your API key (required).
TMAILOR_BASE_URL Only for testing against another API host.

License

MIT

Metadata

Release files for tmailor-mcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tmailor-mcp 0.1.1
File Size Uploaded Provenance
tmailor_mcp-0.1.1.tar.gz 15.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for tmailor-mcp 0.1.1
File Interpreter ABI Platform
tmailor_mcp-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 29.1 kB

Release files / tmailor_mcp-0.1.1.tar.gz

Download URL tmailor_mcp-0.1.1.tar.gz
Size 15.9 kB
Tags Source
SHA-256 checksum
How to use checksums
2bb0056d118e520fa068f76bf40d647ed227462d8173916c1007b723f34c0ad3
BLAKE2b-256 checksum
How to use checksums
609131f798f42b6913f9df07fdffd50d2cbabb9906e1f023e9298e1c669ee116
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / tmailor_mcp-0.1.1-py3-none-any.whl

Download URL tmailor_mcp-0.1.1-py3-none-any.whl
Size 13.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d14522c02bb4ba67337d40732cbbd3759826badfcdeac8b1abe017fd6585874
BLAKE2b-256 checksum
How to use checksums
64aa14868598c20f99e6485d988a85bd66ca4f382a622f3a0c30510c32636b26
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Security for tmailor-mcp 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for tmailor_mcp-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page