imessage-mcp-send 0.1.0__tar.gz

imessage_mcp_send-0.1.0/PKG-INFO

@@ -0,0 +1,65 @@
+Metadata-Version: 2.3
+Name: imessage-mcp-send
+Version: 0.1.0
+Summary: Optional add-on for imessage-mcp: exposes a send_message tool so MCP clients can also send iMessages.
+Keywords: mcp,imessage,macos,claude,llm,send
+Author: moritzhwnr
+Author-email: moritzhwnr <moritz.hawener@gmail.com>
+License: MIT
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Communications :: Chat
+Requires-Dist: imessage-mcp>=0.1.0
+Requires-Dist: typer>=0.25.1
+Requires-Python: >=3.13
+Project-URL: Homepage, https://github.com/yourname/imessage-mcp
+Project-URL: Repository, https://github.com/yourname/imessage-mcp
+Project-URL: Issues, https://github.com/yourname/imessage-mcp/issues
+Description-Content-Type: text/markdown
+
+# imessage-mcp-send
+
+Optional add-on for [`imessage-mcp`](https://pypi.org/project/imessage-mcp/) that adds a `send_message` MCP tool. With this installed, your MCP client can also **send** iMessages, not just read them.
+
+**Sending is irreversible.** Install only if you understand and accept that — and only with an MCP client that surfaces tool calls to you for confirmation before executing them.
+
+## Install
+
+```bash
+uv tool install imessage-mcp-send
+```
+
+This pulls in `imessage-mcp` as a dependency, so you don't need to install it separately.
+
+## Quickstart
+
+```bash
+imessage-mcp-send setup        # opens the macOS Full Disk Access pane
+imessage-mcp-send serve        # MCP server on http://127.0.0.1:8765/mcp
+                               # exposes list_chats, read_messages, search_messages, send_message
+```
+
+On first send, macOS will prompt for **Automation** permission for whatever app is running the CLI (Terminal, iTerm, etc.) to control **Messages**. Click Allow.
+
+## With the broker ([`imessage-bridge`](https://pypi.org/project/imessage-bridge/))
+
+Install both:
+
+```bash
+uv tool install imessage-mcp-send
+uv tool install imessage-bridge
+```
+
+`imessage-bridge serve --public` auto-detects this package and exposes send via your broker URL too.
+
+## The new tool
+
+| Tool | Arguments | Purpose |
+|---|---|---|
+| `send_message` | `text`, `recipient?`, `chat_id?` | Send to a phone/email **or** reply to a 1:1 chat. Group chats not supported. |
+
+## License
+
+MIT

imessage_mcp_send-0.1.0/README.md

@@ -0,0 +1,44 @@
+# imessage-mcp-send
+
+Optional add-on for [`imessage-mcp`](https://pypi.org/project/imessage-mcp/) that adds a `send_message` MCP tool. With this installed, your MCP client can also **send** iMessages, not just read them.
+
+**Sending is irreversible.** Install only if you understand and accept that — and only with an MCP client that surfaces tool calls to you for confirmation before executing them.
+
+## Install
+
+```bash
+uv tool install imessage-mcp-send
+```
+
+This pulls in `imessage-mcp` as a dependency, so you don't need to install it separately.
+
+## Quickstart
+
+```bash
+imessage-mcp-send setup        # opens the macOS Full Disk Access pane
+imessage-mcp-send serve        # MCP server on http://127.0.0.1:8765/mcp
+                               # exposes list_chats, read_messages, search_messages, send_message
+```
+
+On first send, macOS will prompt for **Automation** permission for whatever app is running the CLI (Terminal, iTerm, etc.) to control **Messages**. Click Allow.
+
+## With the broker ([`imessage-bridge`](https://pypi.org/project/imessage-bridge/))
+
+Install both:
+
+```bash
+uv tool install imessage-mcp-send
+uv tool install imessage-bridge
+```
+
+`imessage-bridge serve --public` auto-detects this package and exposes send via your broker URL too.
+
+## The new tool
+
+| Tool | Arguments | Purpose |
+|---|---|---|
+| `send_message` | `text`, `recipient?`, `chat_id?` | Send to a phone/email **or** reply to a 1:1 chat. Group chats not supported. |
+
+## License
+
+MIT

imessage_mcp_send-0.1.0/pyproject.toml

@@ -0,0 +1,34 @@
+[project]
+name = "imessage-mcp-send"
+version = "0.1.0"
+description = "Optional add-on for imessage-mcp: exposes a send_message tool so MCP clients can also send iMessages."
+readme = "README.md"
+license = { text = "MIT" }
+authors = [
+    { name = "moritzhwnr", email = "moritz.hawener@gmail.com" },
+]
+requires-python = ">=3.13"
+dependencies = [
+    "imessage-mcp>=0.1.0",
+    "typer>=0.25.1",
+]
+keywords = ["mcp", "imessage", "macos", "claude", "llm", "send"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: MacOS :: MacOS X",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Communications :: Chat",
+]
+
+[project.urls]
+Homepage = "https://github.com/yourname/imessage-mcp"
+Repository = "https://github.com/yourname/imessage-mcp"
+Issues = "https://github.com/yourname/imessage-mcp/issues"
+
+[project.scripts]
+imessage-mcp-send = "imessage_mcp_send.cli:main"
+
+[build-system]
+requires = ["uv_build>=0.11.2,<0.12.0"]
+build-backend = "uv_build"

imessage_mcp_send-0.1.0/src/imessage_mcp_send/__init__.py

@@ -0,0 +1,10 @@
+"""imessage-mcp-send — adds a send_message tool to the imessage-mcp server.
+
+Importing this package has a SIDE EFFECT: it registers `send_message` on
+the shared FastMCP instance (`imessage_mcp.server.mcp`). Both binaries —
+`imessage-mcp-send` (this package) and `imessage-bridge` (when installed
+alongside) — pick up the tool automatically by importing `tools`.
+"""
+
+# Side-effect import: registers send_message on the shared mcp instance.
+from imessage_mcp_send import tools as tools  # noqa: F401

imessage_mcp_send-0.1.0/src/imessage_mcp_send/cli.py

@@ -0,0 +1,22 @@
+"""Binary `imessage-mcp-send` — same Typer app as `imessage-mcp`, but with
+the `send_message` tool registered on the shared FastMCP instance.
+
+We don't add new Typer commands here. The capability the user installs this
+package for is exposed via the MCP protocol, not the CLI. `serve` from
+imessage-mcp picks up the additional tool automatically because we import
+`imessage_mcp_send` (which triggers `tools` registration) before `app()`
+runs.
+"""
+
+from __future__ import annotations
+
+# Side-effect import: registers send_message on imessage_mcp.server.mcp.
+import imessage_mcp_send  # noqa: F401
+from imessage_mcp.cli import app
+
+# Reflect the upgraded capability in --help.
+app.info.help = "MCP server exposing iMessage (read AND send, local-only)."
+
+
+def main() -> None:
+    app()

imessage_mcp_send-0.1.0/src/imessage_mcp_send/tools.py

@@ -0,0 +1,93 @@
+"""The send_message MCP tool. Side-effect: registers on import.
+
+Sending is irreversible. The MCP client (Claude Desktop, etc.) is expected
+to surface tool calls to the user for confirmation — we don't add our own
+confirmation here because there's no human in the MCP request loop. If
+your client doesn't gate tool use, that's a client issue, not a tool one.
+"""
+
+from __future__ import annotations
+
+import subprocess
+
+# Importing the singleton `mcp` from imessage-mcp's server lets the
+# @mcp.tool() decorator below register on the SAME instance the read-only
+# server already uses. When the server starts, all 4 tools are exposed.
+from imessage_mcp._imessage import open_db
+from imessage_mcp.server import mcp
+
+
+def _send_via_applescript(recipient: str, text: str) -> str:
+    """Run AppleScript to ask Messages.app to send. Returns a result string."""
+    # Pass recipient + text as positional args (not interpolated into the
+    # script source) so a maliciously-crafted message body can't break out
+    # of string literals and inject AppleScript.
+    script = """
+    on run argv
+        set theBuddy to item 1 of argv
+        set theText  to item 2 of argv
+        tell application "Messages"
+            set targetService to 1st service whose service type = iMessage
+            set theBuddy to buddy theBuddy of targetService
+            send theText to theBuddy
+        end tell
+    end run
+    """
+    result = subprocess.run(
+        ["osascript", "-e", script, recipient, text],
+        capture_output=True,
+        text=True,
+    )
+    if result.returncode != 0:
+        return f"ERROR: send failed — {result.stderr.strip() or 'unknown'}"
+    return f"sent to {recipient}"
+
+
+@mcp.tool()
+def send_message(
+    text: str,
+    recipient: str | None = None,
+    chat_id: int | None = None,
+) -> str:
+    """Send an iMessage via Messages.app.
+
+    IRREVERSIBLE side effect. Provide EXACTLY ONE of `recipient` or `chat_id`.
+    Group chats are not currently supported.
+
+    Args:
+        text: The message body to send.
+        recipient: E.164 phone number (e.g. "+491234567890") or iMessage email.
+        chat_id: A chat ID from list_chats. Must be a 1:1 chat.
+
+    Returns: A status string starting with "sent" on success or "ERROR" on failure.
+    """
+    if (recipient is None) == (chat_id is None):
+        return "ERROR: provide exactly one of `recipient` or `chat_id`."
+
+    if chat_id is not None:
+        # Resolve a chat_id to a single handle. AppleScript can technically
+        # address group chats via `text chat id`, but it's unreliable on
+        # modern macOS — better to refuse than half-work.
+        try:
+            conn = open_db()
+        except FileNotFoundError as e:
+            return f"ERROR: {e}"
+        handles = conn.execute(
+            """
+            SELECT h.id FROM chat_handle_join chj
+            JOIN handle h ON h.ROWID = chj.handle_id
+            WHERE chj.chat_id = ?
+            """,
+            (chat_id,),
+        ).fetchall()
+        if not handles:
+            return f"ERROR: no handles found for chat {chat_id}"
+        if len(handles) > 1:
+            return (
+                f"ERROR: chat {chat_id} is a group ({len(handles)} participants); "
+                "group sending is not supported."
+            )
+        recipient = handles[0][0]
+
+    assert recipient is not None  # guaranteed by the XOR check above
+    return _send_via_applescript(recipient, text)