apple-messages-mcp-remote
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind address. Defaults to 127.0.0.1. | 127.0.0.1 |
| MCP_PORT | No | Port to listen on. Defaults to 8443. | 8443 |
| MCP_TRANSPORT | No | Set to 'http' to enable the remote server. Defaults to 'stdio'. | stdio |
| MCP_AUTH_TOKEN | No | Bearer token every request must present. Required when MCP_TRANSPORT=http. Must be at least 32 characters. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chatsA | List recent chats with last message preview and participant info |
| get_chat_messagesB | Get message history for a specific chat |
| search_messagesC | Search messages by text content |
| send_messageA | Send an iMessage or SMS to a phone number or email address |
| get_chat_participantsC | Get participants of a chat |
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 5 tools
list_chats includes participant info and last message preview, which overlaps with get_chat_participants. Similarly, get_chat_messages and search_messages both retrieve messages, though one is chat-scoped and the other is global. Descriptions help but boundaries are not fully crisp.
All tool names follow a consistent verb_noun snake_case pattern: list_chats, get_chat_messages, search_messages, send_message, get_chat_participants. No deviations or mixed conventions.
Five tools is well-scoped for an iMessage server, covering the core messaging actions without unnecessary bloat. Each tool has a clear place in the workflow.
The surface covers listing chats, reading message history, searching, sending, and fetching participants. Minor gaps exist such as deleting messages or retrieving a single chat's full metadata, but the essential workflows are complete.