Purelymail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PURELYMAIL_API_TOKEN | Yes | API token from your Purelymail account settings | |
| PURELYMAIL_READ_ONLY | No | Set to `true` or `1` to expose only the read tools |
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_usersB | Lists all users under the account (up to 1000). |
| get_userB | Retrieves a user's settings: search indexing, recovery, 2FA requirement, spam filtering and password reset methods. |
| create_userC | Creates a new mailbox user on a domain. |
| modify_userB | Changes a user's address, password or settings. Only the fields provided are changed. |
| delete_userA | Permanently deletes a user. |
| list_password_reset_methodsB | Lists a user's password reset methods. The API returns them under a key named |
| upsert_password_reset_methodA | Creates a password reset method, or updates an existing one when existingTarget is given. A reset method can take over the account, so make sure the target belongs to the user. |
| delete_password_reset_methodC | Deletes one of a user's password reset methods. |
| create_app_passwordA | Creates an app password for a user and returns it. The result is a credential: show it to the user once and do not store or repeat it. |
| delete_app_passwordA | Deletes an app password. Requires the full password value; the API has no way to list them. |
| list_routing_rulesA | Lists all routing rules active under the account. |
| create_routing_ruleB | Creates a routing rule for a domain. It must not have the same user/prefix as another rule on that domain. |
| delete_routing_ruleC | Deletes a routing rule. |
| list_domainsA | Lists domains accessible to the account, with their settings and a DNS summary (MX, SPF, DKIM, DMARC). |
| get_ownership_codeA | Gets the value of the DNS ownership proof record required before add_domain will succeed. |
| add_domainB | Adds a domain, provided it passes DNS checks. See get_ownership_code. |
| update_domain_settingsA | Updates settings of an owned domain, and can trigger a DNS recheck. Only the fields provided are changed. |
| delete_domainA | Permanently deletes a domain AND all of its dependent settings and users. Confirm with the user first, listing what will be lost. |
| check_account_creditA | Returns the current account credit as a decimal string with up to 64 digits of precision. |
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
Most tools target clearly distinct resources and actions, making selection straightforward. Minor overlap exists because get_user already returns password reset methods that list_password_reset_methods also exposes, and modify_user versus upsert_password_reset_method requires careful distinction.
The set overwhelmingly follows a verb_noun pattern such as list_users, create_user, delete_domain, and check_account_credit. Small deviations like add_domain instead of create_domain and modify_user versus update_domain_settings keep it from being perfectly consistent.
Nineteen tools is reasonable for a full email-hosting admin surface covering users, domains, routing rules, passwords, and billing. It sits slightly on the heavy side, but each tool appears to earn its place by covering a distinct operation.
The surface covers CRUD for users, domains, routing rules, and password reset methods, plus app-password creation/deletion and account credit. Minor gaps remain: routing rules have no get or update operation, and app passwords cannot be listed, though that appears to be an API limitation.