Skip to main content
Glama
bySherstnev

eXpress MCP connector

by bySherstnev

Related Servers

Alternatives to eXpress MCP connector

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      584 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to list, read, search, and send WhatsApp messages via a persistent WebSocket connection with local SQLite storage.
      40 npm
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables reading, searching, sending iMessages, viewing image attachments, and managing conversations, with full support for modern macOS attributedBody parsing.
      14
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables reading the local iMessage database and sending messages through Messages.app on macOS, with both local stdio and remote HTTP access.
      7
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues