🥢 TempeMail
Zero-config, multi-domain disposable email on Cloudflare Workers.
Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
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.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर 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.