@emailalias/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMAILALIAS_API_KEY | Yes | Your EmailAlias API key. Required for Premium access. | |
| EMAILALIAS_BASE_URL | No | Override base URL for staging/self-hosted. | https://emailalias.io |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_aliasesA | List all email aliases on the authenticated EmailAlias account. Returns id, alias_email, destination_email, active, label, emails_forwarded, emails_blocked. |
| create_aliasA | Create a new email alias. 'random' generates a short code; 'custom' uses custom_code; 'tagged' prepends a random code to a user-provided tag. destination_email must be the user's primary email OR a verified forwarding destination. display_name is Premium-only and shown as the sender on outbound mail. |
| update_aliasA | Update an alias: toggle active (enable/disable) or rename its label. To change the sender display name, use update_alias_display_name (separate 24h-cooldown endpoint). |
| update_alias_display_nameA | Schedule a display-name change on an alias (Premium-only). Edits do NOT take effect immediately — the new value lands in display_name_pending and promotes 24h after the most recent edit. Editing again resets the clock. Capped at 3 edits per rolling 24h per alias. Pass display_name=null (or empty string) to clear; clearing follows the same cooldown. Brand-impersonation patterns (PayPal, Apple, banks, etc.) are rejected with 400. |
| delete_aliasA | Permanently delete an alias. This cannot be undone. Prefer update_alias with active=false if the user might want it back. |
| list_available_domainsA | List domains the user can create aliases on (system domains + their verified custom domains). |
| list_destinationsA | List the user's forwarding destinations (primary email plus verified extras). is_primary=true marks the account email. |
| add_destinationA | Add a new forwarding destination. Triggers a verification email to that address; the destination is unusable until the recipient clicks the link. Premium feature. |
| delete_destinationA | Remove a forwarding destination. Fails with 409 if any alias still forwards to it — reassign those aliases first. |
| send_emailB | Send an email from one of the user's aliases. The recipient sees only the alias address. Requires Premium and a verified, active alias. |
| get_dashboard_statsA | Account-wide counters: total aliases, active aliases, emails forwarded, emails blocked, exposure alerts. |
| list_email_logsA | Paginated email-forwarding log covering the last 90 days. Each item has sender, subject, direction, status, block_reason. |
| list_exposure_eventsA | Suspicious-sender alerts scored against the user's aliases. Use this to identify risky senders and decide which aliases to disable. |
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 13 tools
Every tool targets a distinct resource or action: aliases, display names, destinations, domains, sending, and monitoring are cleanly separated. The potential overlap between update_alias and update_alias_display_name is explicitly disambiguated, and list_email_logs vs list_exposure_events serve clearly different purposes.
Most tools follow a verb_noun snake_case pattern (list_aliases, create_alias, delete_destination, send_email). Minor inconsistencies exist: get_dashboard_stats breaks the list_* convention, and add_destination vs create_alias use different verbs for the same kind of operation.
13 tools is well-scoped for an email alias management server. Each tool covers a meaningful part of the lifecycle without redundant or filler operations, and the count sits comfortably in the ideal range.
The server covers the full alias lifecycle (create, list, update, delete) plus display-name-specific updates, destination management, sending, and monitoring (stats, logs, exposure alerts). No obvious dead ends or critical missing operations for the core domain.