aliasflare

Your own SimpleLogin / addy.io, on Cloudflare's free tier. One-click deploy plus two Email Routing settings, about 5 minutes.

A different email address for every website, all landing in your real inbox. Turn any of them off in one click when the spam starts. Reply as the alias, so your real address never leaks. Verification codes are pulled into the subject line, tracking pixels are stripped, and AI agents can create aliases and read codes through MCP.

中文说明

Why

Features

• Unlimited aliases on one or more of your domains. Create them in the dashboard, or just make one up when signing up — [email protected] is created on first mail (turn off with AUTO_CREATE=false).
• One-click disable. A disabled alias rejects mail as if it never existed.
• Sender hidden, reply as alias. Each message arrives From: "Shop (news at shop.com)" <[email protected]> with a private Reply-To. Hit reply in Gmail and the answer goes out from the alias; your real address is scrubbed from the body too.
• Send new mail from any alias (dashboard, API or MCP).
• Verification codes detected in Chinese, English, Japanese, Korean and more, and put into the subject: [482913] Your login code.
• Tracking pixels removed (1×1 images, hidden images, known trackers).
• MCP server at /mcp: create_alias, get_latest_code, list_aliases, set_alias_enabled, recent_messages, send_from_alias. Let your agent sign up for things without your inbox.
• Never loses mail. If rewriting fails for any reason the original is forwarded as-is.
• Small and auditable. ~1,000 lines of plain JavaScript, one dependency (postal-mime), D1 stores only metadata (no message bodies).

Deploy (about 5 minutes)

You need a domain on Cloudflare.

1. Email Routing on. Cloudflare Dashboard → your domain → Email → Email Routing → enable it (Cloudflare adds the MX records). Under Destination addresses, add your real inbox and click the verification link.
2. Click the button above. Cloudflare copies this repo to your GitHub, creates the D1 database and asks for:
   • DOMAIN — e.g. example.com (comma-separate several)
   • DESTINATION — your verified real inbox
   • ADMIN_TOKEN — a long random password (openssl rand -hex 24)
   • RESEND_API_KEY — optional, see below; none to skip
3. Route mail to the Worker. Email Routing → Routing rules → Catch-all address → action Send to a Worker → aliasflare → enable.

Open your Worker's URL, log in with ADMIN_TOKEN, and create your first alias.

Replying for free

Receiving and forwarding to your own verified inbox is free on every Cloudflare plan. Sending to other people (replies, new mail) needs one of:

• Resend (recommended, free 3,000 emails/month, 100/day): sign up at resend.com, add and verify your domain, create an API key, set it as RESEND_API_KEY.
• Cloudflare Email Sending on Workers Paid ($5/month, 3,000 emails included): onboard your domain under Email Sending and leave RESEND_API_KEY=none.

Without either, everything except replying and sending works.

Manual deploy

git clone https://github.com/charleswei118/aliasflare && cd aliasflare
npm install
npx wrangler d1 create aliasflare        # wrangler can also create it on first deploy
for s in DOMAIN DESTINATION ADMIN_TOKEN RESEND_API_KEY; do npx wrangler secret put $s; done
npm run deploy                            # applies migrations, then deploys

Then do step 3 above.

Settings

Secrets: DOMAIN, DESTINATION, ADMIN_TOKEN, RESEND_API_KEY.
Variables in wrangler.toml:

Use with AI agents (MCP)

{
  "mcpServers": {
    "aliasflare": {
      "url": "https://aliasflare.<you>.workers.dev/mcp",
      "headers": { "Authorization": "Bearer <ADMIN_TOKEN>" }
    }
  }
}

Then: "Sign me up for the Notion newsletter with a new alias and confirm it." The agent calls create_alias(note="notion"), uses the address, then get_latest_code.

Local stdio MCP (Claude Desktop, Cursor, …)

If your client only speaks stdio, run the bundled bridge. It answers tools/list locally and forwards tool calls to your own Worker:

{
  "mcpServers": {
    "aliasflare": {
      "command": "npx",
      "args": ["-y", "github:charleswei118/aliasflare"],
      "env": { "ALIASFLARE_URL": "https://aliasflare.<you>.workers.dev", "ALIASFLARE_TOKEN": "<ADMIN_TOKEN>" }
    }
  }
}

A Dockerfile for the same bridge is included.

REST API

All endpoints need Authorization: Bearer <ADMIN_TOKEN>.

How it works

stranger ──▶ [email protected] ──▶ Worker ──▶ [email protected]
                                   From: "Shop (news at shop.com)" <[email protected]>
                                   Reply-To: reply+<token>@you.com

[email protected] ──▶ reply+<token>@you.com ──▶ Worker ──▶ stranger
                                            From: [email protected]

Only mail from your DESTINATION (and not failing SPF/DMARC) may use a reply+ address.

Limits

• Cloudflare Email Routing: 25 MiB per message. The catch-all rule means the 200-rule limit does not apply.
• Free Workers plan: 100,000 requests/day and 10 ms CPU per invocation; very large messages with many attachments may exceed CPU on the free plan and fall back to plain forwarding.
• Cloudflare Email Sending is in beta.

Development

npm test     # node:test, uses node:sqlite as a D1 stand-in
npm run dev

License

MIT