Get the FREE Ultimate OpenClaw Setup Guide →

mcp -imessage

MCP server for interacting with iMessage on macOS

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio shirhatti-mcp-server-imessage node server.js \
  --env IMESSAGE_API_KEY="your-api-key" \
  --env IMESSAGE_API_SECRET="your-api-secret"

How to use

This MCP server implements bridging for iMessage, enabling you to integrate iMessage messaging capabilities into your MCP workflow. The server exposes a set of tools to send and receive messages, manage conversations, and handle basic messaging actions through the MCP protocol. You can connect to this server from MCP clients or other MCP servers and route messages to iMessage as if you were interacting with a native iMessage channel. Typical usage involves starting the server, authenticating with the provided API credentials, and then issuing MCP commands to send messages, fetch conversation history, or monitor inbound messages from iMessage users.

How to install

Prerequisites:

  • Node.js (LTS version recommended)
  • npm or yarn
  • Access keys/credentials for iMessage integration (as required by the server)

Installation steps:

  1. Clone the repository: git clone https://github.com/SHARED-REPO/shirahatti-mcp-server-imessage.git cd shirhatti-mcp-server-imessage

  2. Install dependencies: npm install

  3. Configure environment variables:

    • Create a .env file or export variables in your environment. At minimum: IMESSAGE_API_KEY=your-api-key IMESSAGE_API_SECRET=your-api-secret
  4. Run the server: node server.js // or, if you have a start script defined in package.json, you can use: npm run start

  5. Verify the MCP setup by connecting a client and performing a simple send/receive test through the MCP protocol.

Additional notes

Notes and tips:

  • Ensure your iMessage API credentials are kept secure and not checked into version control.
  • If you encounter connection errors, verify network access to the iMessage service endpoints and that the API keys are valid.
  • The MCP server may log message IDs, timestamps, and error details; review logs to debug failed sends or inbound messages.
  • If you modify code, consider validating MCP protocol compatibility with your client versions and handling rate limits gracefully.
  • If you need to run this in production, consider a process manager (e.g., pm2) and enabling proper environment-specific configurations (ports, hosts, credentials).

Related MCP Servers

Sponsor this space

Reach thousands of developers