autoMessage MCP Server
Related Servers
Alternatives to autoMessage MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables reading and sending iMessages on macOS through MCP, with tools for managing chats, messages, and attachments via AI agents.MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, sending, and managing iMessage conversations on macOS through MCP.1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to read iMessage history and send messages on macOS. Supports conversation listing, message search with keyword and semantic modes, contact lookup, and sending messages to existing conversations.1311MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, searching, and sending iMessages directly from MCP-compatible clients by accessing the local macOS iMessage database, supporting conversations, attachments, and both individual and group chats.836 npm10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for reading and sending iMessages on macOS. Exposes iMessage history and send capabilities through tools like list_conversations and send_imessage.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets ChatGPT search and read iMessage/SMS history, send one-at-a-time messages, and manage Contacts on your own Mac, with confirmations for any writes.MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct resources: send_imessage, get_draft_status, list_drafts, and cancel_pending_draft form a coherent draft lifecycle with non-overlapping roles. Two mild overlap pairs exist (list_conversations vs list_recent_messages, list_contacts vs find_contact), but the descriptions explicitly differentiate them by scope and use case.
Names are uniformly snake_case with a predictable verb_noun pattern (send_imessage, list_conversations, get_conversation_history, cancel_pending_draft, create_contact). The only deviation is agent_online_check, which is noun-first and lacks a verb, but it remains readable and unambiguous.
Eleven tools is a well-scoped set for an iMessage sending/draft-management server, with each tool covering a necessary operation across sending, drafts, conversations, and contacts. No redundant or filler tools are present.
Core send/draft/read/contact flows are covered, but notable gaps remain: send_imessage addresses recipients rather than conversation GUIDs, so replying into an existing group thread is not clearly supported. Contacts support create but no update or delete, and there is no way to surface or manage read/unread state beyond a filter.