MacOS Only MCP Server That Exposes IMessage Chat
- 2 repo stars
- Updated July 27, 2026
- adelaidasofia/imessage-mcp
imessage-mcp is a MCP server that exposes macOS iMessage chat.db and per-chat exports to your agent over stdio.
About
imessage-mcp is a macOS-only Model Context Protocol server that surfaces Apple iMessage data from chat.db to coding agents such as Claude Code. founders often negotiate deals, support, and partnerships in iMessage, but that context never reaches the agent unless you screenshot or copy paste. This server reads the local database and can export per-chat histories so you can summarize threads, extract action items, or build lightweight personal CRM workflows. Canonical journey placement is grow/support because post-launch conversations dominate, yet the same exports help idea/audience discovery and validate/scope when verbal commitments shape MVP cuts. There is no cloud OAuth—access is entirely local, which aids privacy but demands macOS and Full Disk or appropriate permissions. Treat it as high-sensitivity communication tooling, not a replacement for Help Scout or Intercom. Intermediate complexity reflects Apple privacy gates and the ethics of automating personal messages.
- macOS-only MCP server reading the local iMessage chat.db database
- Exports per-chat message history for agent summarization and search
- stdio MCPB v0.1.0 with no extra env vars in server.json
- Keeps messaging context on your machine rather than a third-party inbox API
- Sensitive personal data—requires explicit trust in local MCP access
MacOS Only MCP Server That Exposes IMessage Chat by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add macOS-onlyMCPserverthatexposesiMessagechat -- npx -y adelaidasofia/imessage-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 27, 2026 |
| Repository | adelaidasofia/imessage-mcp ↗ |
What it does
Expose macOS iMessage history to your agent for summarizing customer chats, exports, and personal CRM workflows—locally from chat.db.
Who is it for?
Best when you handle sales and support over iMessage and want local, agent-assisted recap and export—not a team inbox product.
Skip if: Windows or Linux users, regulated teams that forbid messaging database access, or anyone needing compliant multi-user shared inbox features.
What you get
On macOS, your agent can read exported iMessage histories from chat.db to summarize chats and support you without retyping entire threads.
- Agent-accessible iMessage chat exports from local chat.db
- Summaries and retrieval workflows over per-chat histories without manual copy-paste
By the numbers
- macOS-only server targeting iMessage chat.db
- Server version 0.1.0 stdio MCPB package
- No required environment variables in published server.json
README.md
imessage-mcp
macOS-only MCP server that exposes iMessage history to Claude and exports per-chat conversations into an Obsidian vault. Mirrors the whatsapp-mcp pattern: same hook, same launchd cadence, same vault shape.
Architecture
- Direct read of
~/Library/Messages/chat.db(SQLite, openedmode=ro&immutable=1). No bridge daemon. - Voice-note transcription via Whisper local-cpp (reuses the model already installed for whatsapp-mcp).
- FTS5 incremental search index at
~/.claude/imessage-mcp/search.db. - Vault export per chat into
🤖 AI Chats/iMessage/<Contact>.mdand🤖 AI Chats/iMessage/Groups/<Group>.md. - Send pathway via AppleScript with draft+confirm pattern (no auto-send).
Tool surface
Read: healthcheck, list_chats, list_messages, get_chat, search_contacts, search_messages, get_message_context, get_unread, get_thread, list_attachments, mark_chat_read, export_to_vault.
Write: send_message (drafts an AppleScript send), confirm_send (commits).
Install
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/imessage-mcp
/plugin install imessage-mcp@imessage-mcp
Then grant Full Disk Access to Claude.app (required for chat.db read) and restart Claude Code. Full setup details and env vars in SETUP.md.
Legacy install (manual .mcp.json registration)
See SETUP.md. The short version: grant Full Disk Access to Claude.app, run uv sync, register in vault .mcp.json, restart Claude Code.
Vault export shape
---
type: imessage-chat
contact: "Jane Doe"
phone: "+15555550123"
service: iMessage
chat_guid: "iMessage;-;+15555550123"
message_count: 412
first_message: 2024-08-12
last_message: 2026-05-06
last_sync: 2026-05-07
---
Body sections per date with reactions, edits, replies, voice-note transcripts, and attachment wikilinks.
Related MCPs
Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):
- slack-mcp - multi-workspace Slack
- whatsapp-mcp - WhatsApp via whatsmeow
- google-workspace-mcp - Gmail / Calendar / Drive / Docs / Sheets
- apollo-mcp - Apollo.io CRM + sequences
- substack-mcp - Substack writing + analytics
- luma-mcp - lu.ma events
- parse-mcp - markitdown / Docling / LlamaParse router
- rescuetime-mcp - RescueTime productivity data
- graph-query-mcp - vault knowledge graph queries
- investor-relations-mcp - seed-raise pipeline tracker
- vault-sync-mcp - bidirectional vault sync
Telemetry
This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.
What is sent:
- Plugin name (e.g.
slack-mcp) - Plugin version (e.g.
0.1.0)
What is NOT sent:
- No user identifiers, names, emails, tokens, or API keys
- No file paths, message content, or anything from your work
- No IP address is stored after dedup processing
Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.
Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.
License
MIT.
Built by Adelaida Diaz-Roa. Full install or team version at diazroa.com.
Recommended MCP Servers
A2atlassianJira & Confluence for AI agents.
Abm McpAccount-based marketing for AI agents.1
ACA Automated Client AcquisitionGenerate on-brand content, manage leads, and run outreach across 6 channels from your AI agent.
Activitypub McpRead-only-by-default MCP server: let LLMs explore the Fediverse — Mastodon, Misskey, Pleroma.17
Adaptive Cards McpGenerate, validate, and optimize Adaptive Cards for Teams, Outlook, and Copilot.31Adbloop Meta AdsSafe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.How it compares
Local macOS iMessage database MCP, not Twilio SMS API integration and not a hosted customer-support platform.
FAQ
Who is imessage-mcp for?
Developers on macOS who rely on iMessage for customer and partner communication and want their agent to work from chat.db exports locally.
When should I use imessage-mcp?
Use it when you need summaries, action items, or scope checks from iMessage threads during support, validation, or audience research—not for sending spam at scale.
How do I add imessage-mcp to my agent?
On macOS, install the v0.1.0 imessage-mcp MCPB stdio release from GitHub, grant needed access to Messages data if prompted, and register the server in your MCP client.