Skip to main content
Glama
enesjakozh
marissamarym

iMessage MCP Server

by marissamarym
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

iMessage MCP Server

⚠️ DISCLAIMER - USE AT YOUR OWN RISK ⚠️

This software is provided as-is, without any warranties or guarantees.

An MCP server that uses AppleScript to send iMessages and manage contacts.

This server uses AppleScript to interface with macOS Messages and Contacts apps through the Model Context Protocol (MCP). It wraps AppleScript commands in a TypeScript server to allow you to:

  • View and search your contacts

  • Send iMessages to contacts or phone numbers

  • Get confirmation when messages are sent

Features

Resources

  • Access your contacts via contacts://all

  • View contact details including names, phone numbers, and email addresses

  • All data stays local on your machine

Tools

  • search_contacts - Find contacts by name, phone, or email

    • Takes a search query and returns matching contacts

    • Searches across names, phone numbers, and email addresses

  • send_message - Send an iMessage

    • Takes recipient (phone/email) and message content

    • Sends through your local Messages app

    • Returns confirmation or error details

Related MCP server: imessage-mcp

Installation

  1. Install dependencies:

npm install

  1. Build the server:

npm run build

  1. Configure Claude Desktop to use the server:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "imessage": {
      "command": "node",
      "args": ["/path/to/imessage-server/build/server.js"]
    }
  }
}

  1. Restart Claude Desktop

  2. Grant permissions when prompted for:

    • Contacts access

    • Messages access

Usage

Once installed, you can talk to Claude Desktop naturally:

  • "Show me my contacts"

  • "Search for contacts named Marissa"

  • "Send a message to 555-0123 saying I'll be there in 10 minutes"

  • "Send Alice an iMessage asking if we're still on for lunch"

Security Notes

  • All operations happen locally on your machine

  • No contact or message data is sent to external servers

  • The server requires macOS permissions for Contacts and Messages access

  • Messages are sent through your iMessage account

Development

For development and debugging, use the MCP Inspector:

npx @modelcontextprotocol/inspector node build/server.js

Requirements

  • macOS (for Messages and Contacts integration)

  • Node.js 18 or higher

  • Claude Desktop

  • Active iMessage account

Troubleshooting

If messages aren't sending:

  1. Check Messages app is signed in

  2. Verify permissions are granted

  3. Look for errors in Claude Desktop logs:

tail -f ~/Library/Logs/Claude/mcp*.log

Available Tools

2 tools
search_contactsC

Search contacts by name, phone, or email

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the search functionality but doesn't describe behavioral traits like whether it's read-only, how results are returned (e.g., pagination, format), error handling, or any limitations (e.g., rate limits, authentication needs). This leaves significant gaps for an agent to understand how to use it effectively.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's function without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose and parameters but fails to address behavioral aspects like result format, error conditions, or usage context. For a search tool with no structured behavioral data, more detail is needed to ensure the agent can invoke it correctly.

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

Parameters3/5

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

The input schema has 100% description coverage, with one parameter 'query' documented as 'Search query'. The description adds value by specifying what the query searches ('by name, phone, or email'), which provides context beyond the schema. However, it doesn't detail syntax, examples, or constraints, so it meets the baseline for high schema coverage.

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?

The description clearly states the tool's purpose with a specific verb ('search') and resource ('contacts'), and specifies the searchable fields (name, phone, or email). However, it doesn't explicitly differentiate from the sibling tool 'send_imessage', which appears unrelated but context isn't provided for comparison.

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?

The description provides no guidance on when to use this tool versus alternatives or in what context. It simply states what the tool does without mentioning any prerequisites, exclusions, or scenarios where it's preferred over other methods.

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

send_imessageC

Send an iMessage using Messages app

ParametersJSON Schema
NameRequiredDescriptionDefault
recipientYesPhone number or email of the recipient
messageYesMessage content to send

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Send an iMessage' implies a write/mutation operation, the description doesn't disclose important behavioral aspects: whether this requires specific permissions, if it's synchronous/asynchronous, error conditions, rate limits, or what happens if the recipient isn't in the user's contacts. It mentions 'using Messages app' which provides some implementation context, but lacks operational details.

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

Conciseness5/5

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

The description is extremely concise - a single sentence with zero wasted words. It's front-loaded with the core functionality and uses straightforward language. Every word earns its place, making it easy for an agent to parse quickly while understanding the essential purpose.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after sending (success/failure indicators, return values), doesn't mention authentication requirements, and provides no error handling context. While the purpose is clear, the operational context needed for reliable tool invocation is missing.

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

Parameters3/5

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

The input schema has 100% description coverage, with both parameters ('recipient' and 'message') clearly documented in the schema. The tool description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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?

The description clearly states the action ('Send') and resource ('an iMessage using Messages app'), making the purpose immediately understandable. It doesn't differentiate from the sibling tool 'search_contacts', but that's reasonable since they perform completely different functions. The description is specific enough to understand what the tool does without being tautological.

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?

The description provides no guidance about when to use this tool versus alternatives. There's no mention of prerequisites (like having the Messages app installed or configured), limitations (message length, supported recipients), or comparison with other messaging methods. The agent must infer usage context solely from the tool name and description.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • iMessage MCP Server

    wolfiesch
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude to send and read iMessages on macOS, with smart contact lookup, message history retrieval, and cross-conversation search using natural language commands.
    5
    MIT

  • imessage-mcp

    camfortin
    A
    license
    A
    quality
    C
    maintenance
    A 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.
    6
    MIT

  • imessage-rich-search

    cannavis
    A
    license
    A
    quality
    C
    maintenance
    Enables full-text search of macOS iMessages including link preview metadata. Works as an MCP server for Claude Desktop to search your messages locally.
    1
    MIT

  • imessage-mcp

    jaredmoskowitz
    F
    license
    A
    quality
    D
    maintenance
    A read-only MCP server that exposes your iMessage data to Claude Code and Claude Desktop, with automatic contact name resolution.
    3

Appeared in Searches

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/marissamarym/imessage-mcp-server'

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