Claude Code 및 Claude Desktop에 iMessage 데이터를 노출하고 연락처 이름을 자동으로 확인하는 읽기 전용 MCP 서버입니다.
cd ~/workspace/imessage-mcp
python3.12 -m venv .venv
source .venv/bin/activate
pip install -e .이 서버는 ~/Library/Messages/chat.db 및 연락처 데이터베이스를 읽어야 합니다. 서버를 실행하는 앱에 **전체 디스크 접근 권한(Full Disk Access)**을 부여하세요:
시스템 설정 → 개인정보 보호 및 보안 → 전체 디스크 접근 권한을 엽니다.
Claude Code의 경우: 터미널 앱(예: Terminal, iTerm2, Ghostty)을 추가합니다.
Claude Desktop의 경우: Claude 앱을 추가합니다.
~/.claude/settings.json에 추가하세요:
{
"mcpServers": {
"imessage": {
"command": "/Users/jaredmoskowitz/workspace/imessage-mcp/.venv/bin/python",
"args": ["-m", "imessage_mcp"]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json에 추가하세요:
{
"mcpServers": {
"imessage": {
"command": "/Users/jaredmoskowitz/workspace/imessage-mcp/.venv/bin/python",
"args": ["-m", "imessage_mcp"]
}
}
}Related MCP server: imessage-rich-search
list_chats최근 활동순으로 정렬된 iMessage 채팅 목록을 가져옵니다.
limit (선택 사항, 기본값 50): 가져올 최대 채팅 수
get_messages특정 채팅의 메시지를 가져옵니다.
chat_id (필수): list_chats에서 확인한 채팅 식별자
limit (선택 사항, 기본값 50): 최대 메시지 수
since (선택 사항): ISO 날짜 문자열 — 해당 날짜 이후의 메시지만 가져옴
search_messages모든 채팅에서 키워드가 포함된 메시지를 검색합니다.
query (필수): 검색할 텍스트
limit (선택 사항, 기본값 50): 최대 결과 수
"내 그룹 채팅 목록을 보여줘" "Business Ideas 채팅에서 최근 메시지 20개를 가져와" "내 메시지에서 'startup idea'를 검색해줘"
Get messages from a specific iMessage chat.
Args: chat_id: The chat identifier (from list_chats) limit: Maximum number of messages to return (default 50) since: Only return messages after this ISO date (e.g. '2024-01-15' or '2024-01-15T10:30:00')
| Name | Required | Description | Default |
|---|---|---|---|
| chat_id | Yes | ||
| limit | No | ||
| since | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It describes a read operation with filtering, but omits details like rate limits, permissions, or whether messages are sorted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two short paragraphs: one for purpose, one for parameters. No unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with output schema, the description covers the key aspects: what it does and what each parameter does. Could mention sorting or pagination, but not essential.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage; the description adds crucial meaning by explaining chat_id as from list_chats, limit with its default, and since with ISO date examples.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets messages from a specific iMessage chat, distinguishing it from sibling search_messages by specifying the chat_id is obtained from list_chats.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by stating chat_id comes from list_chats and provides limit/since filters, but does not explicitly compare to search_messages or advise when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List iMessage chats sorted by most recent activity.
Args: limit: Maximum number of chats to return (default 50)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions sorting by activity but does not disclose if it requires authentication, rate limits, pagination, or that it is read-only. It adds minimal behavioral context beyond the action itself.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely terse: one sentence for purpose and one for the parameter. Every sentence earns its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, output schema available), the description covers the essential purpose and parameter semantics. It lacks mention of sorting direction but 'most recent activity' implies descending. Mostly complete for a simple list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains the 'limit' parameter as 'Maximum number of chats to return (default 50)', adding meaning beyond the schema's type and default. With 0% schema coverage, this compensates adequately, though other implicit constraints are not mentioned.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List iMessage chats sorted by most recent activity', using a specific verb and resource, and is differentiated from sibling tools (get_messages, search_messages) which focus on individual messages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like get_messages or search_messages, nor any context for selection or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search all iMessage chats for messages containing the query text.
Args: query: The text to search for limit: Maximum number of results to return (default 50)
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| limit | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It only states that it searches all chats, without detailing performance, pagination, error handling, or what happens with empty queries or limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, with two sentences and a bullet list. It front-loads the core purpose. However, it could be more structured (e.g., separate sections) to improve readability for complex use cases.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 parameters, no nested objects) and the presence of an output schema, the description is mostly adequate. However, it lacks usage context and any mention of return structure, leaving some gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description adds only minimal clarification: 'The text to search for' for query and 'Maximum number of results to return (default 50)' for limit. This adds little beyond the schema's title fields, failing to compensate for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches all iMessage chats for messages containing the query text, specifying the verb 'search', resource 'iMessage chats', and scope 'all'. It distinguishes from siblings 'get_messages' (which likely retrieves specific messages) and 'list_chats'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool vs. its siblings ('get_messages', 'list_chats'), nor are there any prerequisites or exclusions mentioned. The agent is left to infer usage context without explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0get_messageslist_chatssearch_messagesScored across 3 tools
Each tool targets a distinct operation: listing chats, retrieving messages from a specific chat, and searching across all chats. There is no functional overlap.
All tool names follow a consistent verb_noun pattern using snake_case (list_chats, get_messages, search_messages), making the set predictable.
Three tools is appropriate for the server's scope, covering essential read operations without being too few or excessive.
The tool set provides solid coverage for reading iMessage data. A potential minor gap is the lack of a send message tool, but that may be intentional for a read-only server.
MCP connector for iMessage & Contacts via a local Mac agent + Vercel relay
Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Your own WhatsApp as an MCP server: read, search and send from any MCP client.