@wirebox-sh/mcp
Related Servers
Alternatives to @wirebox-sh/mcp
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 gradedqualityAmaintenanceEnables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP agents to send and receive iMessages via BlueBubbles, allowing human-in-the-loop oversight and replies from a phone.2 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.1 npm5MIT

AgentTrust MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to use email, instant messaging, and cloud file storage via MCP tools, giving each agent a verified identity with its own email address, real-time chat, and file sharing capabilities.52 npm1MIT- FlicenseBqualityBmaintenanceEnables external AI agents to read, send, and manage email over IMAP/SMTP via MCP, including inbox listing, search, drafts, scheduled/batch sending, and operations like reply, archive, and labels.303-
TDQS
Scored across 6 tools
Each tool targets a distinct action: sending vs listing emails, sending iMessages, listing conversations, fetching message history, and getting identity/status. There is no overlap between tools that could cause an agent to select the wrong one.
All tools follow a consistent wirebox_{channel}_{action} pattern with snake_case. Minor inconsistency exists: mail_list doesn't specify what is listed (messages), while imessage uses list_conversations and get_messages, but the pattern is still predictable.
Six tools is well-scoped for a messaging server covering two channels (email and iMessage) plus identity/status. Each tool has a clear purpose and none are redundant.
Core messaging workflows are supported: send and list email, send iMessage, list conversations, and fetch messages. Minor gaps exist such as no single-email fetch, no email reply, or no mark-as-read, but agents can accomplish primary tasks.