PurelyMail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PURELYMAIL_API_KEY | Yes | Your PurelyMail API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_userD | Creates a user. Creates a new user. |
| delete_userC | Deletes a user. Deletes a user. |
| list_usersC | Lists all users under your account.. Lists all users under your account (up to 1000). |
| modify_userD | Modifies a user. Modifies a user. |
| get_userC | Gets a user. Retrieves details of a user. |
| create_or_update_password_reset_methodC | Creates or updates a password reset method (either phone or email). |
| delete_password_reset_methodC | Deletes a password reset method. |
| list_password_reset_methodsC | Lists all password reset methods for a user. |
| create_routing_ruleB | Creates a new routing rule for a domain. Routing rule must not have the same user/prefix as any other existing rules for the domain. |
| delete_routing_ruleC | Deletes an existing routing rule |
| list_routing_rulesA | Lists all routing rules active under your account |
| add_domainC | Adds a domain.. Adds a domain, assuming it passes DNS checks. |
| get_ownership_codeA | Gets ownership code record. Gets the DNS record value of the Purelymail ownership proof record, required to add a domain |
| list_domainsC | Lists domains accessible to an account.. Lists domains accessible to an account, possibly including shared domains. |
| update_domain_settingsC | Updates settings for a domain. Updates settings for an existing owned domain. |
| delete_domainB | Delete Domain. Deletes a domain, and all dependent settings and users. |
| create_app_passwordC | Creates an app password. Creates a new app password. |
| delete_app_passwordC | Deletes app password. Deletes an app password. |
| check_account_creditC | Returns current account credit.. Returns current account credit, as a BigDecimal string with precision 64. |
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 19 tools
Each tool targets a distinct resource and action: users, domains, routing rules, password reset methods, app passwords, ownership proof, and account credit are clearly separated. No two tools appear to perform the same operation.
Most tools follow a readable snake_case verb_noun pattern with consistent pluralization. Minor deviations exist in verb choices such as add_domain vs create_user, modify_user vs update_domain_settings, and check_account_credit vs get_user.
Nineteen tools is somewhat heavy for an account administration surface, and the count is driven by several small resource groups. Most tools are justified, but it sits at the upper end of what feels comfortably scoped.
Core resources have solid coverage: users have full CRUD, domains have add/list/update/delete, and routing rules plus password reset methods have create/delete/list operations. Minor gaps exist, such as no list_app_passwords and no direct update for routing rules, though most can be worked around.