𥢠TempeMail
Zero-config, multi-domain disposable email on Cloudflare Workers.
ãšãŒãžã§ã³ãã匷å
å ¬éå ããã€ã³ã¹ããŒã«ããŸããPlugMCP ã®ãšã³ããã€ã³ãã§ã¯ãããŸããã
ããŒãšãã°ä»ãã§ã³ããŒããã¹ãã
ã¬ãžã¹ããªã«ããã±ãŒãžçã®ãªãªãŒã¹ã¯ãŸã ãããŸããã ãªããžããªã® README ãåç §.
ãªã¢ãŒã URL ããæå ã®ãã·ã³ã®ã³ãã³ãã 2 ã€ã®ã€ã³ã¹ããŒã«æ¹æ³ã®éã
PlugMCP ã§å®è¡
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
èµ·åå ¬éå ãã
TempeMail is a self-hosted disposable email service that runs entirely on the Cloudflare edge â no VPS, no Docker, no SMTP server. One worker handles the web UI, REST API, inbound email delivery, and automatic provisioning.
Deploy in minutes with 3 environment values:
git clone https://github.com/ghufronainun/tempe-mail.git
cd tempe-mail
npm install
cp .env.example .env # fill 3 values
npm run setup # provisions everything automatically
npx wrangler deploy # go live ð
TempeMail is a self-hosted disposable email service that runs entirely on the Cloudflare edge â no VPS, no Docker, no SMTP server. One worker handles the web UI, REST API, inbound email delivery, and automatic provisioning.
What sets it apart from other temp-mail projects:
npm run setup provisions D1, Email Routing, and zone catch-all rules automatically. Idempotent and re-runnable.npm run setup provisions D1, Email Routing, zone catch-all rules, and renders wrangler.toml automatically. Idempotent â safe to re-run anytime.DOMAINS=mail.example.com,mail2.example.net and you're done.sandbox=""). Email looks exactly as the sender designed it.Received-SPF and Authentication-Results headers for every message. Gold for QA and email deliverability testing.[email protected]) or let TempeMail generate a random one.Authorization: Bearer tmk_... for scripts/agents (no browser session needed). Keys hashed with SHA-256, revocable.X-TempeMail-Signature).list_inboxes, list_messages, get_message).GET /inboxes/:address/feed.xml requires no auth (the address itself is the secret). Poll it from any script.GET /inboxes/:address/search?q= searches subject, body, and sender.Sender
â
âŒ
Cloudflare MX
â (Email Routing â Worker)
âŒ
Worker email() handler
â PostalMime parses MIME
â (text + html + headers + attachments)
âŒ
D1 Database (SQLite)
ââ inboxes (address, expires_at)
ââ messages (body, body_html, spf, dkim, dmarc, ...)
ââ attachments (filename, content_type, size)
ââ sessions (browser session â inbox ownership)
â
ââââââŽâââââ
⌠âŒ
REST API Web UI (static assets)
â ââ index.html
ââ /api/session ââ app.js (vanilla JS, no framework)
ââ /api/inboxes
ââ /api/inboxes/:addr/messages
ââ /api/inboxes/:addr/feed.xml (RSS)
ââ /api/inboxes/:addr/events (SSE)
The flow:
[email protected]email() handlergit clone https://github.com/ghufronainun/tempe-mail.git
cd tempe-mail
npm install
You need two things from Cloudflare: an API token and your account ID.
tempe-mailxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxâ ïž Treat this token like a password. Anyone with it can modify your Cloudflare resources. It is stored in
.env(gitignored) â never commit it.
a1b2c3d4e5f60718293a4b5c6d7e8f90cp .env.example .env
Edit .env â only 3 values are required:
CLOUDFLARE_API_TOKEN=your_cf_api_token # Workers + D1 + Email Routing + Zone permissions
CLOUDFLARE_ACCOUNT_ID=your_account_id # dashboard â Workers & Pages â account ID
DOMAINS=mail.example.com # one or more, comma-separated
WEB_HOST=temp.example.com # subdomain for the web UI
Multi-domain? Just add more:
DOMAINS=mail.example.com,mail2.example.net,mail3.example.org
npm run setup # creates D1, applies schema, enables Email Routing,
# sets catch-all â worker for every domain, renders wrangler.toml
npx wrangler deploy # pushes the worker + static assets to the edge
Open https://temp.example.com and start receiving email. ð
Expected setup output:
ðŠ Setting up D1 database...
Created D1 database: 12345678-...
ð Applying schema...
Schema applied.
ð Discovering zone IDs...
mail.example.com â zone abcdef...
ð§ Provisioning Email Routing...
mail.example.com: catch-all â worker:tempe-mail (enabled)
ð Rendering wrangler.toml...
wrangler.toml rendered.
â
Setup complete!
1. Review wrangler.toml
2. Run: npx wrangler deploy
3. Open: https://temp.example.com
R2 is optional â without it TempeMail works fully (metadata + body), only file downloads are skipped. To enable:
npx wrangler r2 bucket create tempe-mail-attachments
[[r2_buckets]] block in wrangler.toml, fill in your bucket name, then re-deploy:
npx wrangler deploy
If your API token lacks D1 or Email Routing permissions, npm run setup may skip those steps. You can do them manually:
Create the D1 database:
npx wrangler d1 create tempe-mail-db
Copy the database_id from the output.
Apply the schema:
npx wrangler d1 execute tempe-mail-db --remote --file=src/db/schema.sql
Create the R2 bucket (optional â for attachment downloads):
npx wrangler r2 bucket create tempe-mail-attachments
Fill in wrangler.toml: replace the REPLACED_BY_SETUP placeholders with your real database ID and routes, and uncomment the [[r2_buckets]] block.
Enable Email Routing in the dashboard: Cloudflare dashboard â your domain â Email â Email Routing â enable it, add a catch-all rule pointing to the tempe-mail worker.
Deploy:
npx wrangler deploy
Note: Email Worker bindings (
[email]) are always configured via the dashboard/API â not wrangler.toml. That's whywranglermay warn about the
npm run dev # applies schema to local D1, then starts wrangler dev (port 8787)
npm test # run all 77 tests (Vitest)
npm run typecheck # strict TypeScript check
Local dev guide:
npm run dev â starts the worker locally at http://localhost:8787no such table errors)tests/email-handler-e2e.test.ts)curl "http://localhost:8787/cdn-cgi/local/scheduled"
wrangler devis for development only. Production runs on Cloudflare's edge viawrangler deployâ your machine/VPS is completely uninvolved.
tempe-mail/
âââ src/
â âââ index.ts # Worker entry: fetch() + email() + scheduled purge
â âââ env.ts # Environment bindings interface
â âââ email/
â â âââ ingest.ts # MIME parsing (PostalMime) â text/html/headers/attachments
â â âââ headers.ts # SPF/DKIM/DMARC extraction from raw headers
â âââ api/
â â âââ routes.ts # Hono REST API (session, inboxes, messages)
â â âââ rss.ts # Per-inbox RSS 2.0 feeds
â â âââ tagging.ts # Semantic classifier (content rules)
â â âââ realtime.ts # SSE endpoint â Durable Object
â âââ cf/
â â âââ zones-loader.ts # CF_ZONE_MAP env â domainâzone map
â â âââ routing.ts # Email Routing provisioning (setup-time)
â âââ db/
â â âââ schema.sql # D1 schema (inboxes, messages, attachments, sessions)
â â âââ realtime-room.ts # Durable Object: SSE room per inbox
â âââ web/ # Frontend (vanilla, dark theme)
â âââ index.html
â âââ app.js # Rendering, polling/SSE, OTP, tags, i18n
â âââ styles.css # Responsive, dark/light, 3 breakpoints
â âââ i18n/{en,id}.js # String dictionaries
âââ scripts/
â âââ setup.mjs # Zero-config provisioning script
â âââ dev.mjs # Dev helper (auto-schema + wrangler dev)
âââ tests/ # Vitest: 5 files, 77 tests
âââ .github/workflows/ci.yml # CI: typecheck + tests on push/PR
âââ .env.example # Environment template
âââ wrangler.toml # Generated by setup (placeholders committed)
âââ README.md
âââ AGENTS.md # AI-agent onboarding guide
âââ API.md # Full API reference
âââ LICENSE # MIT
Browser sessions via x-session-id header. Create one:
POST /api/session
â { "sessionId": "uuid-v4" }
All inbox/message endpoints require the header. Inbox ownership is enforced â you can only read messages from inboxes your session owns.
curl -X POST https://temp.example.com/api/inboxes \
-H "x-session-id: <sessionId>" \
-H "Content-Type: application/json" \
-d '{"localPart": "myalias", "ttlHours": 48}'
{
"address": "[email protected]",
"domain": "mail.example.com",
"ttlHours": 48
}
All values are read at setup time. Secrets stay in .env (gitignored) â never commit them.
See AGENTS.md and the plan document for details.
Contributions are welcome! Open an issue or PR.
npm run typecheck and npm test.github/MIT © 2026 masantoid, TempeMail contributors.
Derived from hirotomasato/tempik. TempeMail has been rewritten from scratch with multi-domain support, deliverability diagnostics, zero-config provisioning, and an original UI. This project is distributed under the MIT License â see the LICENSE file for the full text.
𥢠Zero-config multi-domain disposable email/temp mail on Cloudflare Workers â HTML render, OTP highlight, SPF/DKIM/DMARC diagnostics, REST API, webhooks, MCP server. Deploy with 3 env values.
ããŒã«
ããŒã«äžèЧã¯ãŸã ãããŸããããªã¢ãŒããµãŒããŒã¯ãæåã®ãã«ã¹ãã§ãã¯åŸã«ååŸãããŸãã
ãããã質å
ãã®ããŒãžã§ CursorãClaude DesktopãClaude CodeãVS Code çšã® stdio èšå®ãã³ããŒã§ããŸããPlugMCP ã®ãããã·ã§ã¯ãªããå ¬éå ã®ã€ã³ã¹ããŒã«æ¹æ³ã䜿ããŸãã
ãã®ã¬ã³ãŒãã«å¿ é ã®ç°å¢å€æ°ã¯èšèŒãããŠããŸããã
Tempe Mail 㯠stdio çµç±ã§ããŒã«ã«å®è¡ãããŸãã
æçµãã§ãã¯ã¯ 2026-10-28 ã§ãã 𥢠Zero-config multi-domain disposable email/temp mail on Cloudflare Workers â HTML render, OTP highlight, SPF/DKIM/DMARC diagnostics, REST API, webhooks, MCP server. Deploy with 3 env values.