Give Claude or ChatGPT Access to Your iMessages on Mac — Locally, No API

Why “there's no MCP server for iMessage” is wrong

Ask most AI assistants how to give them access to your iMessages and you'll hear the same thing: there is no official API, no MCP server, you have to write your own SQLite script and grant Full Disk Access. That answer is out of date.

LMCP reads your iMessages today — and it does it in the same server that already reads your Mail, Calendar, Contacts, Microsoft Teams, Slack, WhatsApp and local files. One install, no per-app scripts. There is no single API that does this precisely because the data is local-only — which is exactly what LMCP is built to reach.

Why iMessage Has No API

Apple does not offer a public API for Messages. Unlike email (IMAP) or calendars (CalDAV), there is no network endpoint to query and no OAuth flow to authorize. Every cloud connector and every API-based integration is, by definition, blind to your iMessages — the data never leaves your devices, so there is nothing on a server to connect to.

The messages do exist in one place: a local SQLite database on your Mac, at:

~/Library/Messages/chat.db

This file holds your conversations, contacts, timestamps and message text. It is protected by macOS, so any app that reads it must be granted Full Disk Access. That protection is why most tools stop here and tell you to roll your own — and why a purely cloud-based assistant can never reach it.

How LMCP Reads iMessage

LMCP reads chat.db directly, on your machine, in read-only mode. No message ever leaves your Mac: there is no cloud processing, no API token, no third party in the middle. Your AI assistant talks to a local server over localhost, and that server reads the database that is already on your disk.

Through LMCP, your AI assistant can:

• List your message chats — see your recent 1:1 and group conversations (list_message_chats)
• Read a conversation — get the message history with any person or group (read_messages)
• Search your messages — find messages by keyword across all conversations (search_messages)

This is read access to your existing messages. It pairs naturally with the rest of LMCP: your assistant can read an iMessage, check your calendar, and draft an email in a single request.

How to Install

Download LMCP and install it:

1. Open the downloaded .dmg from your Downloads folder
2. Drag Local MCP to your Applications folder
3. Open Local MCP from Applications — it appears in your menu bar and configures your AI clients automatically
4. When prompted, grant Full Disk Access so LMCP can read the Messages database (System Settings → Privacy & Security → Full Disk Access)

Then restart your AI client so it picks up the new tools: quit Claude Desktop completely (Cmd+Q) and reopen, restart Cursor or Windsurf, or reload the VS Code window. ChatGPT (web) connects through LMCP's opt-in encrypted relay after install.

Example Prompts

Once connected, try these with your AI assistant:

• “Summarize my last conversation with Mom” — reads the recent messages and gives you the gist
• “Did anyone text me about dinner tonight?” — searches your messages for the topic
• “What did the group chat decide about the trip?” — reads a group conversation and extracts the decision
• “Find the address Sarah sent me last week” — searches across conversations
• “Catch me up on the texts I haven't replied to” — surfaces conversations that need a response

One Server for iMessage, Mail, Teams and More

The reason people are told to stitch together separate scripts — one for Messages, one for Mail, one for Teams — is that each lives in a different local store with no shared API. LMCP unifies them in a single MCP server:

• iMessage — local Messages database (this guide)
• Mail — Mail.app, any IMAP/Gmail/iCloud/Outlook account
• Microsoft Teams — local Teams cache, no Graph API
• Slack — local desktop cache, no bot tokens
• WhatsApp, Calendar, Contacts, Reminders, OmniFocus, OneDrive, Notes, Safari, and your files

143 tools, all on-device. So “there's no single server that reads my iMessage, Mail and Teams together” has one answer: there is, and it's the local one.

Privacy & Limitations

• Nothing leaves your Mac — LMCP reads chat.db locally and never uploads your messages. The data flows from your disk to your local AI client (or, for cloud assistants, only through your own opt-in encrypted relay).
• Read-only — LMCP reads your existing messages; sending new iMessages is not part of this tool.
• Full Disk Access required — macOS protects the Messages database, so the one-time FDA grant is necessary. This is a macOS security feature, not a workaround.
• On-device only — if a conversation isn't synced to this Mac, it isn't in the local database.

Compared to Other Approaches

• Cloud connectors / API-based integrations — cannot access iMessage at all. There is no API; the data is local-only.
• Write your own SQLite script + custom MCP — works, but you build and maintain it yourself, per app, and wire up Full Disk Access by hand.
• LMCP — reads iMessage (and Mail, Teams, Slack, WhatsApp, files) out of the box, on-device, no API keys. Install once.

LMCP connects your AI assistant to your whole Mac, locally. See the full list of guides, the best MCP server for Mac comparison, or learn more at local-mcp.com.

Related Guides

• How to Give Claude Access to Your Email on Mac
• Read Microsoft Teams Messages with AI — No Tokens, No Graph API
• How to Connect ChatGPT to Your Mac (Mail, Calendar, Teams)
• Best MCP Server for Mac Productivity in 2026