Skip to main content
Glama
tarun101

iMessage MCP

by tarun101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to iMessage MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • MessagesBridge

      IsaiahDupree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets ChatGPT search and read iMessage/SMS history, send one-at-a-time messages, and manage Contacts on your own Mac, with confirmations for any writes.
      MIT

    • imessage_mcp

      jtcorbett
      F
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for macOS Messages + Contacts: send messages, read chat history, wait for replies, and manage Contacts.app entries.
      1
      -

    • imessage-mcp

      camfortin
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that enables reading iMessage conversations and sending new messages through Claude Desktop. It provides secure, read-only access to your Mac's iMessage database and AppleScript-based message sending capabilities.
      6
      MIT

    • lane-mac-mcp

      lanemiles
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only iMessage MCP server for macOS that lets you list conversations, read chats, and search message history through Claude or a CLI. It is auditable, dependency-light, and deliberately has no send capability.
      -

    • iMessage MCP

      4ndylg
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for local macOS Messages database, enabling querying of chats, messages, attachments, and metadata.
      210 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.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    list_chats and search_messages are distinct, but get_messages and get_recent_messages have potentially confusingly similar purposes—both return recent messages newest first and differ mainly in scope (single conversation vs. all conversations). The descriptions clarify the difference, but an agent could easily pick the wrong one without careful reading.

    Naming Consistency5/5

    All four tools consistently follow a clear snake_case verb_noun pattern (list_chats, get_messages, get_recent_messages, search_messages). The verbs are distinct and descriptive, with no mixing of conventions or styles.

    Tool Count5/5

    Four tools is well-scoped for a read-only iMessage server: one for chat discovery, two for message retrieval (per-chat and global), and one for search. Each tool earns its place with no bloat.

    Completeness2/5

    The read surface is decent, but the server is called iMessage and list_chats explicitly references a send_to_chat tool that is absent, leaving a significant dead end for agents wanting to send messages. Search also admits to missing newer attributedBody messages, so coverage feels incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources