MacOS Only MCP Server That Exposes IMessage Chat
Expose macOS iMessage history to your agent for summarizing customer chats, exports, and personal CRM workflows—locally from chat.db.
Overview
imessage-mcp is a MCP server for the Grow phase that exposes macOS iMessage chat.db and per-chat exports to your agent over stdio.
What is this MCP server?
- 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 server targeting iMessage chat.db
- Server version 0.1.0 stdio MCPB package
- No required environment variables in published server.json
Community signal: 1 GitHub stars.
What problem does it solve?
Critical customer and cofounder conversations live in iMessage where your coding agent cannot see them, so follow-ups and scope decisions miss context.
Who is it for?
Solo macOS builders who 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Direct messages are where early customers and friends give unfiltered feedback; grow/support is the shelf for conversational context, with validate/idea use when scoping from real threads. Support fits because the server reads iMessage chat.db and exports per-chat history for triage and follow-up, not for shipping app binaries.
How it compares
Local macOS iMessage database MCP, not Twilio SMS API integration and not a hosted customer-support platform.
Common Questions / FAQ
Who is imessage-mcp for?
Indie 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.