Skip to main content
Glama
duanefields

iMessage MCP

by duanefields
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to iMessage MCP

No user-submitted related servers found.

    Related Servers

    • Apple Messages MCP

      dh-repo
      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

    • multimodal-imessage-mcp

      tszaks
      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

    • iMessage MCP Server

      sameelarif
      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.
      258 npm
      10
      MIT

    • imsg

      ml-lubich
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Read, search, and send iMessages locally from your terminal or through MCP clients like Claude, Cursor, and VS Code.
      -

    • imessage-mcp-server

      tinyxia
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for reading and sending iMessages on macOS. Exposes iMessage history and send capabilities through tools like list_conversations and send_imessage.
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of iMessage: listing chats, reading messages, searching, participants, unread, attachments, and sending. There is no overlap in purpose, and the descriptions clarify boundaries (e.g., get_messages excludes tapbacks, get_attachments only lists metadata).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_chats, get_messages, search_messages, get_participants, get_unread, get_attachments, send_message. The verbs are uniform (list/get/search/send) and nouns are clear, making the set predictable.

    Tool Count5/5

    Seven tools is well-scoped for an iMessage server: it covers the core read and send operations without redundancy. Each tool earns its place, and the count is within the ideal 3-15 range.

    Completeness4/5

    The surface covers the main iMessage workflows: listing chats, reading/searching messages, checking unread, viewing participants and attachments, and sending. The only notable gap is the inability to start a new conversation, which is explicitly documented and may be a platform limitation, but it is a real dead end for reaching new contacts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources