Skip to main content
Glama
thenavidm

iMessage MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
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

    • jons-mcp-imessage

      jonmmease
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read iMessage history and send messages on macOS. Supports conversation listing, message search with keyword and semantic modes, contact lookup, and sending messages to existing conversations.
      13
      11
      MIT

    • iMessage RAG MCP

      jaredtkatz
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve from your local macOS iMessage history using hybrid retrieval with context expansion, all processed locally without sending data off-device.
      -

    • iMessage MCP Server

      viraatdas
      F
      license
      A
      quality
      D
      maintenance
      Enables reading, searching, and sending iMessages on macOS by accessing the local messages database and utilizing AppleScript. Users can list conversations, search message history, and send messages to individuals or group chats directly through the Model Context Protocol.
      6
      -
    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

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct purposes: STT (transcribe_voice_note) vs TTS (speak), sending (send_message/send_file), receiving (inbox), and querying (search_messages/list_conversations/get_conversation). The reading tools overlap somewhat—inbox, get_conversation, and search_messages all return messages—but descriptions differentiate them by scope and cursor semantics.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (transcribe_voice_note, search_messages, list_conversations, get_conversation, resolve_contact, send_message, send_file), but several deviate: bare verb 'speak' and bare nouns 'inbox' and 'server_status'. Mixed conventions across the set, though each name is individually readable.

    Tool Count5/5

    Ten tools is well-scoped for a messaging server that combines send/receive, search, read, contact lookup, voice transcription, TTS, and diagnostics. Each tool earns its place without redundancy.

    Completeness4/5

    Core messaging lifecycle is covered: send text/files, receive via inbox, search history, list/read conversations, resolve contacts, plus STT/TTS and status. Minor gaps exist—no message edit/delete, reactions, or group-chat administration—but agents can handle typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources