Purelymail MCP
Related Servers
Alternatives to Purelymail MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables management of LWS client accounts through MCP clients like Claude, Cursor or Codex, covering domains, DNS records and propagation checks, hosting plans, renewals and contacts via the full LWS Client API. Purchases and write operations stay off unless explicitly enabled, with read-only and sandbox modes available.26MIT
- AlicenseCqualityCmaintenanceProvides AI assistants with access to PurelyMail's email management API, enabling user, domain, routing, and billing management through natural language.19106 npm14MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose problems within an Octopus instance, and optionally create releases, deploy releases, run runbooks, and adjust feature toggles through MCP tools.547 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides a secure MCP gateway for AI agents to access APIs without exposing raw credentials, with scoped access, audit logging, and OAuth support.MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to read, search, sort, draft, and send email from connected mailboxes through MCP tools, with access controlled by per-token permissions.183MIT
- AlicenseNot gradedqualityCmaintenanceLets AI assistants read cookieless website analytics and manage goals, alerts, and uptime checks through a hosted MCP endpoint with permission-scoped access tokens.MIT
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.