simplelogin-mcp
Related Servers
Alternatives to simplelogin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server that enables reading, sending, and automating Proton Mail via Bridge, with optional SimpleLogin alias management.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes SimpleLogin alias management endpoints, enabling creation, listing, searching, updating, and toggling email aliases with configurable permission levels.MIT
- AlicenseAqualityAmaintenanceUnofficial MCP server for Stalwart Mail Server using the JMAP management API, providing 39 tools to read and manage mailboxes, accounts, domains, DKIM, queue, IP filtering, and admin operations.391MIT
- AlicenseAqualityCmaintenanceUnofficial MCP server for Proton Mail (not affiliated with Proton AG) — send, read, search & organize email over SMTP/IMAP3166 npm6MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Proton privacy suite — Mail, Pass, Drive, Calendar, and VPN. 36 tools for Claude and other MCP-compatible AI agents.22MIT
- AlicenseNot gradedqualityCmaintenanceA self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.MIT
TDQS
Scored across 27 tools
Each tool targets a distinct resource/action combination; alias, mailbox, contact, custom-domain, notification, settings, and account operations are clearly separated. Overlaps like alias_create_random vs alias_create_custom and alias_update vs alias_set_enabled are disambiguated by descriptions and different intent.
Names are consistently snake_case and mostly follow a resource_action or resource_subresource_action pattern. Minor deviations exist: alias_domains_list uses a plural subresource with list-last while alias_list is singular, and account_get_info vs settings_get differ in verb placement.
27 tools is on the heavy side for an MCP server, exceeding the typical 3-15 range. The breadth is justified by SimpleLogin's many resource types, but the surface is large enough that count feels borderline rather than well-scoped.
Core lifecycle coverage is strong: aliases, mailboxes, contacts, settings, and notifications have read/write/delete or state-change operations. Gaps remain around custom-domain creation/deletion and fewer CRUD operations for some secondary resources, but agents can work around most of them.