IMessage MCP vs Mobilerun

A side-by-side look at the IMessage MCP and Mobilerun MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

IMessage MCP logoIMessage MCPOS Automation · Local subprocess (stdio)25 tools for searching, analyzing, and exploring your iMessage history on macOS.59GoodAuth: not declaredMobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.49FairAuth: not declared

Verdict: choose IMessage MCP for os automation work as a local process; choose Mobilerun for os automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

IMessage MCP logoChoose IMessage MCP when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_messages, get_conversation, list_conversations.
Explore IMessage MCP

Mobilerun logoChoose Mobilerun when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Mobilerun

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIMessage MCP logoIMessage MCPMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal59/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars289,746
Directory activity 3 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools8Not listed

Tools & capabilities

IMessage MCP tools 8

  • search_messagesSearch by substring, exact text, token, or phrase. Message text by default; conversation names and attachment filenames are opt-in. Filter by service, sent or received, and date
  • get_conversationRead a conversation by `chat_id` or by a contact or group name, with edits, reactions, receipts, replies, group events, and attachments. The cursor pages to older events
  • list_conversationsFind conversations by contact, service, kind, reply state, or date, each with its latest message, newest first or by who you text most
  • get_attachmentShow one attachment from `get_conversation`: images as a JPEG with location and camera metadata removed, text files as text. Needs the `full` privacy mode
  • sync_messagesPull every change since a cursor: new, edited, unsent, and deleted messages, conversation memberships, reactions, and receipts
  • analyze_communicationMessage counts by hour and weekday, response times, streaks, and who starts conversations
  • resolve_contactMatch a name, phone number, or email to a contact in your Mac's Address Book, and report ambiguity rather than guess
  • server_statusVersion, update availability, privacy mode, index and cache state, schema support, conversation membership counts, and Contacts access

Mobilerun tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

IMessage MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "imessage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "imessage-mcp@latest"
      ]
    }
  }
}

Mobilerun

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobilerun": {
      "command": "uvx",
      "args": [
        "mobilerun"
      ]
    }
  }
}

Frequently asked questions

IMessage MCP is categorized under OS Automation and uses a local stdio subprocess. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick IMessage MCP for os automation work and Mobilerun for os automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

IMessage MCP has no declared pricing — check the project's own site. Mobilerun has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add imessage-mcp and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, IMessage MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 28 GitHub stars. Mobilerun has 49/100 (Fair) with 7 views, 0 installs and 9,746 GitHub stars.