aliasflare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALIASFLARE_URL | No | Your aliasflare Worker URL, e.g. https://aliasflare.yoursub.workers.dev. Optional. | |
| ALIASFLARE_TOKEN | No | Your aliasflare ADMIN_TOKEN. Optional; no credentials required for tools/list. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_aliasA | Create a new forwarding email alias on the user's own domain, e.g. for signing up to a website without revealing the real address. Mail sent to the alias is forwarded to the user's inbox. Returns the new address. Pass |
| list_aliasesA | List the user's aliases, newest first, with note, enabled state and forwarded/blocked counts. Optional |
| set_alias_enabledA | Turn an alias off (mail to it is rejected as if it never existed — use this to stop spam) or back on. |
| get_latest_codeA | Return the most recent one-time verification code (OTP) received by an alias within the last |
| recent_messagesA | Show recent mail activity (sender, subject, code, direction) — metadata only, no bodies. Optional |
| send_from_aliasA | Send a plain-text email to someone FROM one of the user's aliases, so the real address stays hidden. Requires RESEND_API_KEY or Cloudflare Email Sending. This sends real mail: only call it when the user asked to send this exact message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: create, list, toggle, fetch OTP, view activity, and send. The only slight overlap is between get_latest_code and recent_messages, both of which can surface verification codes, but their descriptions clarify that one is OTP-focused and the other is broader activity metadata.
Most names follow a verb_noun pattern (create_alias, list_aliases, set_alias_enabled, get_latest_code, send_from_alias), making them predictable. recent_messages is the lone noun-phrase outlier, but it remains readable and consistent enough in tone.
Six tools is a well-scoped set for an email alias service, covering creation, listing, state control, code retrieval, activity review, and sending. No tool feels redundant or extraneous for the stated purpose.
The core lifecycle is covered: create, list, enable/disable, read verification codes, view recent messages, and send from an alias. Minor gaps exist, such as a permanent delete operation and the ability to update an alias note, but agents can reasonably work around these using the disable toggle.