imessage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_conversationsA | List recent conversations (individual and group) with resolved contact names. Shows group chats with participant counts. |
| get_messagesA | Read messages from a conversation. Search by contact name, phone number, email, or group name. Shows resolved sender names in group chats and includes attachment info. |
| search_messagesA | Search all messages for a keyword or phrase. Shows resolved contact names and attachment info. |
| send_messageA | Send a message (iMessage, SMS, or RCS) to a contact or group chat. Accepts contact names, phone numbers, emails, or chat GUIDs. Can also send file attachments. |
| get_chat_participantsA | Get participants of a chat with resolved contact names. Useful for group chats. |
| get_attachmentsA | Get attachments (images, files, links) from a conversation. Filter by mime type (e.g. 'image' for photos, 'application/pdf' for PDFs). Returns file paths that can be read or saved. |
| save_attachmentA | Save/copy a message attachment to a destination (defaults to Desktop). Use after get_attachments to save files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of messaging: listing conversations, reading messages, searching, sending, viewing participants, and handling attachments. No two tools have overlapping purposes, making selection unambiguous.
All tools follow a consistent verb_noun naming pattern (e.g., get_conversations, send_message, search_messages), making the API predictable and easy to navigate.
With 7 tools, the server is well-scoped for an iMessage interface, covering the core workflows without unnecessary bloat or insufficient functionality.
The tool set covers the essential lifecycle of messaging: listing, reading, searching, sending, and managing attachments. No critical operations are missing for the stated purpose.