Carbon Voice
Related Servers
Alternatives to Carbon Voice
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables reading, searching, sending iMessages, viewing image attachments, and managing conversations, with full support for modern macOS attributedBody parsing.141MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents on macOS to securely read and search the local Messages database, catch up on missed messages via a persistent inbox, and send texts or files to allowlisted chats, with optional voice note transcription and text-to-speech.MIT
- FlicenseNot gradedqualityDmaintenanceLets you search personal messages and contacts, and send messages to individuals or groups through Claude.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, search, and send iMessages with features like contact name resolution, session grouping, and attachment listing. It provides intent-aligned tools to efficiently navigate conversation history and manage messages through natural language queries.6MIT

bluereacher-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to send iMessages, check delivery status, read conversations, and verify iMessage capability over a dedicated line.4133 npmMIT- FlicenseAqualityBmaintenanceEnables reading and searching a user's eXpress chats and message history locally, with optional confirmed sending of text messages.4-
TDQS
Scored across 42 tools
Most tools have distinct purposes, and the detailed USE INSTEAD notes clarify boundaries. However, a few pairs are easy to confuse: search_user vs search_users (singular/plural), suggest_action_items_from_message vs suggest_action_items_from_messages (singular/plural, sync/async), and get_folder vs get_folder_with_messages. These are distinguishable but require careful reading.
Names are all snake_case and mostly verb_noun, but the verbs vary widely: list, get, create, update, delete, set, move, search, run, summarize, add, suggest. Some names are quite long (run_ai_action_for_shared_link, search_messages_by_heard_status) and the verb_prefix is not uniform (search_user vs list_messages vs get_conversation). Overall readable but not a tight pattern.
42 tools is high for a single server, but the domain spans messages, conversations, folders, action items, AI actions, share links, users, and workspaces, so the scope is broad. Still, several tools are near-duplicates that could be merged (search_user/search_users, get_folder/get_folder_with_messages, the two suggest_action_items variants), which suggests the surface could be tightened to ~30 tools.
The tool set covers most lifecycle operations for the core entities: messages (create, list, get, move, attach, share), folders (create, get, update, delete, move), action items (create, list, get, update, delete, set status, suggest), and AI actions (list, run, get responses). Minor gaps: no tool to delete a conversation, no way to update a message's transcript, and no explicit tool to revoke a share link (only via error handling). These are workaroundable.