Blujay MCP Server
OfficialRelated Servers
Alternatives to Blujay MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to send SMS/iMessage and check replies via Sendblue API using secure polling (no webhooks).4-

Blooio MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to send and receive iMessage, SMS, RCS, and WhatsApp messages, and to manage channels, numbers, contacts, chats, groups, calls, 10DLC registration, support tickets, webhooks, and the event feed through one tool per Blooio API operation. Supports OAuth sign-in with organization-scoped access or a Blooio API key.Apache 2.0- 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.7MIT

iBlueText MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to send real iMessage, SMS, and WhatsApp messages from a business's dedicated number, run campaigns, read replies and lead scores, manage contacts and sequences, and check which numbers are iPhones or on WhatsApp. It is available as a hosted OAuth connector for Claude and ChatGPT or as a local npm package with an API key that adds SMS verification, verify widgets, and reply webhooks.407 npmMIT
bluereacher-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to send iMessages, check delivery status, read conversations, and verify iMessage capability over a dedicated line.412 npmMIT- 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
TDQS
Scored across 19 tools
Most tools target a distinct resource+action (send_message, react_to_message, edit_message, unsend_message, mark_conversation_read are cleanly separable), and descriptions explicitly disambiguate near-neighbors like list_conversations vs. find_unanswered and get_conversation vs. get_message. A few boundaries require reading the descriptions carefully (e.g. get_account vs. list_conversations filtered by on_number, check_imessage vs. send_message service selection), but no two tools appear to do the same thing.
Every tool follows a strict snake_case verb_noun pattern (get_, list_, find_, send_, create_, update_, save_, mark_, set_, opt_out_). No mixed conventions or stray camelCase anywhere in the set.
19 tools is slightly above the comfortable 3-15 band, but each maps to a genuinely distinct capability of a messaging platform (send, react, edit, unsend, read receipts, typing, groups, contacts, webhooks, docs). Nothing looks like filler, though a couple of peripheral tools could be consolidated.
Core messaging lifecycle is well covered: discovery (contacts, conversations), send, delivery inspection, reactions, edit/unsend, read state, group management, opt-out, and docs search. The notable gap is the webhook lifecycle — you can list and create subscriptions but not update, delete, or inspect a single subscription, which will force agents to work around dead subscriptions.