Browse
→ Communication
→ Aliasflare MCP
Aliasflare MCP
Manages self-hosted email aliases, retrieves verification codes and can send mail through a Cloudflare Worker. Requires a domain on Cloudflare, Email Routing, D1 and a private admin token. Outbound mail needs a separately configured sending provider. MCP access includes send and alias-control tools, so treat the token as privileged and require approval before sending. Public repository created November 1, 2026.
MCP unverified
Integration
| Transport | stdio |
| Auth | api-key |
| Endpoint | npx -y github:charleswei118/aliasflare |
| Install | Deploy your own Worker with D1 and Email Routing using the README, then privately configure ALIASFLARE_URL and ALIASFLARE_TOKEN and register npx -y github:charleswei118/aliasflare; retain approval prompts for outbound mail |
Use Cases
| 01 | Create a separate alias for a service |
| 02 | Read the latest verification code |
| 03 | Disable an alias receiving unwanted mail |
| 04 | Review recent message metadata |
Tags
email-aliases cloudflare-workers verification-codes self-hosted
Machine-readable: /api/servers.json
· JSON-LD schema embedded in <head>