← ClaudeAtlas

imessagelisted

Apple Messages client for macOS. Use when the user mentions iMessage, Messages, texting or texts, their message history, a conversation with someone by name or number, sending someone a message or file, catching up on what they missed, or transcribing a voice note.
navidmoazzez/imessage-mcp · ★ 0 · AI & Automation · score 70
Install: claude install-skill navidmoazzez/imessage-mcp
# iMessage 10 tools for Apple Messages on macOS: an inbox that survives restarts, search across full history, contact resolution, sending with delivery confirmation, and local voice-note transcription. macOS only. Reading needs Full Disk Access; sending needs permission to automate Messages. ## Before anything else Run `server_status` if anything behaves oddly. It reports whether the database is reachable, where the cursor sits, how many contacts loaded, and which optional tools are installed. A first `inbox` call on a fresh install initialises the cursor at the current end of history and returns nothing. That is correct, not a failure. Messages from that point on appear on the next call. ## Catching up `inbox` returns everything since the last call and then advances a cursor stored on disk. Two consequences worth holding onto. **It is consuming.** Anything it returns will not be returned again. Summarise or act on what comes back in the same turn. Use `peek: true` to look without consuming. **It includes the user's own sends by default.** Note-to-self is the normal way people use this, and those rows are written as `is_from_me = 1`. Pass `includeFromMe: false` only when the user explicitly wants incoming messages alone. ## Reading history `search_messages` takes any combination of `query`, `from`, `chatId`, `since` and `until`. Prefer it over `get_conversation` when the user is asking what someone said rather than to read a thread. `list_conversations` first when