iMessage MCP Server
Related Servers
Alternatives to iMessage MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables full-text search of macOS iMessages including link preview metadata. Works as an MCP server for Claude Desktop to search your messages locally.1MIT
- FlicenseAqualityDmaintenanceA read-only MCP server that exposes your iMessage data to Claude Code and Claude Desktop, with automatic contact name resolution.3-
- AlicenseAqualityDmaintenanceConnects Claude Desktop to iMessage on macOS, enabling reading conversations, searching messages, sending texts, and managing attachments.77 npmMIT
- AlicenseAqualityCmaintenanceA local MCP server that enables reading iMessage conversations and sending new messages through Claude Desktop. It provides secure, read-only access to your Mac's iMessage database and AppleScript-based message sending capabilities.6MIT
- AlicenseNot gradedqualityCmaintenanceA local server that lets Claude Desktop or Claude Code read, search, triage and draft messages, view and add calendar events, and look up or create contacts, all signing in with a single Apple app-specific password. It defaults to drafting rather than sending and offers a read-only mode, plus recipient allowlists, so nothing changes or leaves your account unless you explicitly allow it.PolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityCmaintenanceA read-only iMessage MCP server for macOS that lets you list conversations, read chats, and search message history through Claude or a CLI. It is auditable, dependency-light, and deliberately has no send capability.-
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one searches contacts and the other sends messages. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun pattern (search_contacts, send_imessage) with clear, descriptive names that align with their actions. No deviations or mixed conventions are present.
With only two tools, the server feels thin for an iMessage domain, lacking essential operations like reading messages, managing conversations, or handling attachments. The count is too low for comprehensive coverage.
The toolset is severely incomplete for an iMessage server. It misses core functionalities such as retrieving messages, listing conversations, replying to threads, or deleting messages, leaving significant gaps that will hinder agent workflows.