Skip to main content
Glama
viraatdas

iMessage MCP Server

by viraatdas

send_message

Send text messages to phone numbers or email addresses using iMessage on macOS through the MCP server.

Instructions

Send an iMessage to a phone number or email address.

Args: recipient: Phone number (e.g. +15551234567) or email address text: Message text to send

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipientYes
textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the send_message tool, which uses AppleScript to send an iMessage.
    async def send_message(recipient: str, text: str) -> str:
        """Send an iMessage to a phone number or email address.
    
        Args:
            recipient: Phone number (e.g. +15551234567) or email address
            text: Message text to send
        """
        escaped_recipient = _escape_applescript(recipient)
        escaped_text = _escape_applescript(text)
    
        script = (
            'tell application "Messages"\n'
            f'  send "{escaped_text}" to buddy "{escaped_recipient}" '
            'of (service 1 whose service type is iMessage)\n'
            "end tell"
        )
    
        proc = await asyncio.create_subprocess_exec(
            "osascript", "-e", script,
            stdout=asyncio.subprocess.PIPE,
            stderr=asyncio.subprocess.PIPE,
  • server.py:236-236 (registration)
    MCP tool registration for send_message.
    @mcp.tool()
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to clarify delivery confirmations, rate limits, thread creation behavior, or error scenarios beyond the basic 'Send' verb which merely restates the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with clear purpose statement. The 'Args:' block is slightly unconventional for MCP descriptions but efficiently documents parameters without verbosity. No wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 2-parameter tool with existing output schema (per context signals), but gaps remain regarding sibling differentiation ('send_group_message') and iMessage-specific behaviors (e.g., blue bubble failures, read receipts). Minimum viable but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Compensates well for 0% schema description coverage by documenting both parameters. Provides valuable format example for recipient ('+15551234567') and clarifies text content. Does not cover constraints (e.g., character limits, supported media types) preventing a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action ('Send') and resource ('iMessage') with specific target types (phone number or email). However, it does not explicitly distinguish from sibling tool 'send_group_message'—the singular 'a phone number' offers only implicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this versus 'send_group_message' or other messaging siblings. No mention of prerequisites (e.g., contact requirements), platform restrictions (Apple ecosystem), or failure conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/viraatdas/imessage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server