Aliasflare MCP
Manage self-hosted email aliases through a Cloudflare Worker and expose the configured service to an MCP client.
Overview
Aliasflare is a self-hosted email alias service built around Cloudflare Workers, D1 and Email Routing. Its project documentation describes forwarding mail, replying from an alias and exposing alias operations to an MCP client. Each deployment has its own Worker address. A client that supports remote MCP can use the deployed Worker’s MCP route. The repository also documents a local stdio bridge for clients that use that transport.
Getting started
Follow the repository’s deployment and Email Routing steps for your Cloudflare account, then configure the client with your own Worker address or the documented bridge.
Frequently asked questions
Is there a single shared MCP endpoint?
The repository documents a route on your own deployed Worker. Use the address assigned to your deployment.
What if my MCP client only supports stdio?
The project documents a bundled stdio bridge that forwards tool calls to your Worker.