eXpress MCP connector
Related Servers
Alternatives to eXpress MCP connector
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables read-only access to your own eXpress desktop chats through the app's debug inspector, including listing and reading chats, searching full message history, reading threads, and saving attachment previews or full files. It cannot send messages and requires the desktop app to be running and signed in.10MIT
- AlicenseAqualityCmaintenanceEnables an agent to read the user's local Messages.app database on macOS, listing chats and threads and searching iMessage/SMS history entirely on localhost, with optional AppleScript sending gated behind an explicit flag. Access is read-only and scoped-shut by default, and replies can be optionally sent when send mode is enabled.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables macOS agents to read eXpress chats and threads, search contacts, send messages and attachments, and download verified files through MCP, while a Keychain-backed session broker manages authentication.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to search and read macOS Messages history from a local chat database, including conversations, unread messages, and Contacts-based names. It is read-only, runs over stdio, and cannot send, edit, or delete messages.MIT
- 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.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list, read, search, and send WhatsApp messages via a persistent WebSocket connection with local SQLite storage.49 npmAGPL 3.0
TDQS
Scored across 4 tools
Each tool has a clearly separate purpose: listing conversations, checking session status, reading message history, and sending messages. There is no meaningful overlap between express_list_chats and express_get_history because one identifies chats and the other retrieves messages within a specific chat.
Tools consistently use the express_ prefix with a verb_noun structure, such as express_list_chats, express_get_history, and express_send_message. The only minor deviation is express_status, which uses a noun without an explicit verb like check.
Four tools is well-scoped for a chat connector focused on listing, reading, sending, and session status. Each tool serves a necessary function in the core workflow without unnecessary bloat.
The core chat workflow is covered: list chats, read paginated history, and send messages, plus a session status check. Missing advanced features like creating/deleting chats or managing messges are not essential for the apparent read-and-send scope.