imessage

v0.1.0

iMessage channel for Claude Code — reads chat.db directly, sends via AppleScript. Built-in access control; manage pairing, allowlists, and policy via /imessage:access.

Claude Code2 skills1 MCP serverstdio

33.3kupdated 13 minutes ago

Source

$ git clone https://github.com/anthropics/claude-plugins-official

Clone the source, then follow the repository's marketplace instructions for your runtime. The plugin root is external_plugins/imessage/ inside the repository.

Layout

external_plugins/imessage/

├── .claude-plugin/plugin.json
├── skills/access/SKILL.md
├── skills/configure/SKILL.md
└── .mcp.json

Skills2

accessskills/access/SKILL.md

Manage iMessage channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the iMessage channel.

configureskills/configure/SKILL.md

Check iMessage channel setup and review access policy. Use when the user asks to configure iMessage, asks "how do I set this up" or "who can reach me," or wants to know why texts aren't reaching the assistant.

MCP servers1

imessagestdio

command: bun
args: run --cwd ${CLAUDE_PLUGIN_ROOT} --shell=bun --silent start

MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.

Manifests1

external_plugins/imessage/.claude-plugin/plugin.json

{
  "name": "imessage",
  "description": "iMessage channel for Claude Code — reads chat.db directly, sends via AppleScript. Built-in access control; manage pairing, allowlists, and policy via /imessage:access.",
  "version": "0.1.0",
  "keywords": [
    "imessage",
    "messaging",
    "channel",
    "mcp"
  ]
}