fmsg-mcp
Related Servers
Alternatives to fmsg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access a self-hosted MAX messenger personal account: browse chats, read and search message history, inspect context, pins and forwarded text, download attachments, and send text or files with receipts and retry protection. Also supports durable batch state for scheduled workflows, with local authentication and access control over Streamable HTTP.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, schedule, and organize messages across multiple IMAP/SMTP accounts, with real-time inbox watching, verification-code capture, calendar extraction, and analytics. It supports provider-aware label management, OAuth2, and both local stdio and networked Streamable HTTP transports.25 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, and organize email across multiple IMAP/SMTP accounts, including drafts, labels, bulk operations, real-time mailbox watching, verification-code capture, calendar extraction, and analytics. It runs locally over stdio or as a networked Streamable HTTP service with OAuth2 sign-in and provider auto-detection.25 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, schedule, and organize mail across multiple IMAP/SMTP accounts, including drafts, provider-aware labels, analytics, calendar extraction, and real-time inbox watching with verification-code capture. Runs over stdio or Streamable HTTP and supports auto-detected providers, OAuth2, and multi-account operation.25 npmISC

Pombus MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate permission-scoped email inboxes over stdio, including reading and searching threads, labeling, composing drafts, sending when permitted, and managing lists and metrics while keeping humans in the review loop.820 npmMIT- AlicenseAqualityBmaintenanceDM / IM for AI agents over the A2A 1.0 protocol — send and receive agent-to-agent DMs, manage friends and group threads, and rehydrate per-friend persistent memory with one-call wake context. 12 tools, pip install agoradm-mcp, stdio transport.121Apache 2.0
TDQS
Scored across 18 tools
Each tool has a clearly distinct target action: received vs sent listing, single message vs thread retrieval, send vs reply vs draft lifecycle, and delivery vs reaction vs transient status. Adjacent concepts such as reply/send_message and react/indicate are explicitly differentiated in the descriptions, so an agent should not misselect.
The set mostly follows a snake_case verb-first pattern such as send_message, create_draft, mark_read, and download_attachment. There are minor deviations like delivery_status, whoami, and bare verbs reply/react/indicate, but the naming remains predictable and readable.
18 tools is slightly above the ideal 3-15 range, but the messaging domain reasonably needs separate operations for drafts, threads, delivery state, attachments, reactions, waiting, and address resolution. Most tools earn their place rather than duplicating functionality.
The surface covers core messaging workflows: receive/list/read, send/reply, draft lifecycle, threads, attachments, delivery status, reactions, and blocking waits. Minor gaps remain, such as message search, forwarding, or editing an existing draft, but agents can work around them.