Skip to main content
mcpSource-backed

Mac Messages MCP Server

macOS Messages MCP server that lets Claude read recent conversations, search messages, inspect contacts and chats, fetch attachments, and send iMessage or SMS/RCS messages.

by Carter Lasalle · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://raw.githubusercontent.com/carterlasalle/mac_messages_mcp/main/README.md, https://github.com/carterlasalle/mac_messages_mcp
Brand
Mac Messages MCP
Brand domain
github.com
Safety notes
Mac Messages MCP can send real outbound iMessage or SMS/RCS messages through the signed-in macOS Messages app., Confirm recipient, contact match, group chat ID, message text, delivery method, and timing before allowing `tool_send_message`., Read tools query the local Messages SQLite database and AddressBook data; they require Full Disk Access and can expose broad conversation history., Attachment tools can return image bytes inline or local filesystem paths for non-image, large, audio, video, PDF, or other files., Proxy or container bridge setups can expose the local Messages server to other processes or networks; bind narrowly and add authentication if used.
Privacy notes
Tool calls can expose message text, timestamps, participants, phone numbers, email addresses, contact names, group chat names, chat IDs, attachment metadata, filenames, MIME types, local paths, and inline image data., Messages may contain personal, medical, legal, financial, work, customer, family, or authentication information., Fetched attachment paths and inline images can reveal private media, documents, screenshots, PDFs, audio, or video files., MCP client logs and model context may retain conversation snippets, contact matches, message-search queries, and outbound message drafts.
Author
Carter Lasalle
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Includes a review or approval gate.

0/6 ready
Install & runtime1Configuration1Permissions & scopes3Review & approval115 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 3 risk areas. Review closely: network access.

3 areas
  • SafetyNetwork accessMac Messages MCP can send real outbound iMessage or SMS/RCS messages through the signed-in macOS Messages app.
  • SafetyGeneralConfirm recipient, contact match, group chat ID, message text, delivery method, and timing before allowing `tool_send_message`.
  • SafetyLocal filesRead tools query the local Messages SQLite database and AddressBook data; they require Full Disk Access and can expose broad conversation history.
  • SafetyLocal filesAttachment tools can return image bytes inline or local filesystem paths for non-image, large, audio, video, PDF, or other files.
  • SafetyNetwork accessProxy or container bridge setups can expose the local Messages server to other processes or networks; bind narrowly and add authentication if used.
  • PrivacyLocal filesTool calls can expose message text, timestamps, participants, phone numbers, email addresses, contact names, group chat names, chat IDs, attachment metadata, filenames, MIME types, local paths, and inline image data.
  • PrivacyGeneralMessages may contain personal, medical, legal, financial, work, customer, family, or authentication information.
  • PrivacyLocal filesFetched attachment paths and inline images can reveal private media, documents, screenshots, PDFs, audio, or video files.
  • PrivacyNetwork accessMCP client logs and model context may retain conversation snippets, contact matches, message-search queries, and outbound message drafts.

Disclosure: MIT-licensed Python MCP server published as the `mac-messages-mcp` package. This entry is distinct from chat-platform and notification entries because it reads the local macOS Messages database and sends through the user's Messages app via local macOS permissions.

Safety notes

  • Mac Messages MCP can send real outbound iMessage or SMS/RCS messages through the signed-in macOS Messages app.
  • Confirm recipient, contact match, group chat ID, message text, delivery method, and timing before allowing `tool_send_message`.
  • Read tools query the local Messages SQLite database and AddressBook data; they require Full Disk Access and can expose broad conversation history.
  • Attachment tools can return image bytes inline or local filesystem paths for non-image, large, audio, video, PDF, or other files.
  • Proxy or container bridge setups can expose the local Messages server to other processes or networks; bind narrowly and add authentication if used.

Privacy notes

  • Tool calls can expose message text, timestamps, participants, phone numbers, email addresses, contact names, group chat names, chat IDs, attachment metadata, filenames, MIME types, local paths, and inline image data.
  • Messages may contain personal, medical, legal, financial, work, customer, family, or authentication information.
  • Fetched attachment paths and inline images can reveal private media, documents, screenshots, PDFs, audio, or video files.
  • MCP client logs and model context may retain conversation snippets, contact matches, message-search queries, and outbound message drafts.

Prerequisites

  • macOS with Messages configured for iMessage, SMS, or RCS delivery.
  • Python 3.10 or newer and uv for the recommended `uvx` launch path.
  • Full Disk Access granted to the terminal, Claude Desktop, Cursor, or other host application that runs the MCP server.
  • Contacts or AddressBook permission if using contact lookup.
  • Automation permission for Messages before sending outbound messages.
  • Review of which conversations, attachments, contacts, and group chats may be exposed to the MCP client.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
MIT-licensed Python MCP server published as the `mac-messages-mcp` package. This entry is distinct from chat-platform and notification entries because it reads the local macOS Messages database and sends through the user's Messages app via local macOS permissions.
Full copyable content
{
  "mcpServers": {
    "messages": {
      "command": "uvx",
      "args": ["mac-messages-mcp"]
    }
  }
}

About this resource

Content

Mac Messages MCP Server connects Claude and other MCP clients to the local macOS Messages app. It can read recent messages, search conversations, list group chats, resolve contacts, check iMessage availability, search attachment metadata, fetch attachments, and send outbound messages through Messages.

Use it when a macOS automation workflow needs local Messages context or explicitly approved outbound messaging. Because it reads personal communications and can send real messages, start with read/search workflows and require confirmation for every outbound send.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, PyPI metadata, license, package metadata, MCPB manifest, server tool definitions, Messages implementation, and registry metadata for current setup and operating details.

Features

  • Read recent Messages within a configurable time window.
  • Filter recent messages by contact, phone number, email address, or group chat ID.
  • Fuzzy-search message content with match scoring.
  • Find contacts by fuzzy name matching.
  • Check Messages database, Contacts, and AddressBook access diagnostics.
  • List named group chats and chat IDs.
  • Check whether a recipient appears reachable through iMessage.
  • Send one outbound message to an individual contact or group chat.
  • Search attachment metadata by date range, contact, MIME type, and limit.
  • Fetch attachments by ID, returning small images inline or local paths for larger and non-image files.
  • Normalize common phone-number formats before sending.
  • Run as a local Python MCP server through uvx.
  • Package an MCPB extension for Claude Desktop from the repository manifest.

Installation

Grant Full Disk Access to the host application that will run the server, then add it to an MCP client:

{
  "mcpServers": {
    "messages": {
      "command": "uvx",
      "args": ["mac-messages-mcp"]
    }
  }
}

Use diagnostic tools first:

tool_check_db_access
tool_check_addressbook
tool_check_contacts

Only after permissions and contact matching are verified should you allow outbound message sends.

Use Cases

  • Summarize recent messages from a specific contact or group chat.
  • Search older conversations for a phrase, decision, date, or attachment.
  • Find a contact before drafting a response.
  • Retrieve an image or document attachment after confirming the attachment ID.
  • Check whether a number is reachable through iMessage.
  • Draft and send a single confirmed message through the local Messages app.
  • Build local notification, follow-up, or personal assistant workflows on macOS.

Safety and Privacy

Mac Messages MCP Server touches personal communications. Full Disk Access can expose the local Messages database, Contacts permission can expose address-book entries, and attachment fetches can expose private media or documents. Keep message reads scoped by contact, time window, or chat ID whenever possible.

The send tool has real-world consequences. Confirm ambiguous contact matches, group chat IDs, recipient phone numbers, message body, and whether the message will use iMessage, SMS, or RCS before sending. Do not run network-exposed proxy setups without authentication and tight binding.

Duplicate Notes

Existing catalog entries cover WhatsApp, Telegram, LINE, and general messaging workflows. This entry covers the separate carterlasalle/mac_messages_mcp project and mac-messages-mcp package for local macOS Messages database access, attachment retrieval, contact lookup, and outbound Messages app sends.

Source citations

Add this badge to your README

Show that Mac Messages MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/mac-messages-mcp-server.svg)](https://heyclau.de/entry/mcp/mac-messages-mcp-server)

How it compares

Mac Messages MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

macOS Messages MCP server that lets Claude read recent conversations, search messages, inspect contacts and chats, fetch attachments, and send iMessage or SMS/RCS messages.

Open dossier

macOS app and bundled stdio MCP server that lets Claude access selected local services such as Calendar, Contacts, Messages, Location, Maps, Reminders, camera, microphone, screenshots, Shortcuts, utilities, and Weather.

Open dossier

MCP server for running AppleScript and JavaScript for Automation on macOS, with a searchable knowledge base of automation recipes for apps, files, browsers, system settings, Terminal, and productivity workflows.

Open dossier

MCP server for controlling Adobe After Effects through a local Node bridge and ScriptUI panel for compositions, layers, keyframes, expressions, masks, and effects.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandiMCP logoiMCP
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorCarter LasalleMatttPeter SteinbergerDakkshin
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesMac Messages MCP can send real outbound iMessage or SMS/RCS messages through the signed-in macOS Messages app. Confirm recipient, contact match, group chat ID, message text, delivery method, and timing before allowing `tool_send_message`. Read tools query the local Messages SQLite database and AddressBook data; they require Full Disk Access and can expose broad conversation history. Attachment tools can return image bytes inline or local filesystem paths for non-image, large, audio, video, PDF, or other files. Proxy or container bridge setups can expose the local Messages server to other processes or networks; bind narrowly and add authentication if used.iMCP can expose highly sensitive personal macOS services to Claude through MCP tools. Calendar, Contacts, Reminders, and Shortcuts tools can create, update, or run actions, not only read data. Capture tools can take pictures, record microphone audio, and capture screenshots when the corresponding service is enabled and macOS permission is granted. Messages access can read local message history after the user grants access to the Messages database. The app can add or update the iMCP entry in Claude Desktop MCP configuration while preserving other server entries. Enable only the services needed for a task and do not mark clients as trusted unless you want repeated connections to bypass prompts.macOS Automator MCP executes AppleScript or JavaScript for Automation through `osascript`, either from inline script content, an absolute script path, or a knowledge-base script ID. AppleScript and JXA can control local applications, read and write files, run shell commands through scripting additions, manipulate browser tabs, send keystrokes, change settings, and trigger app-specific actions depending on macOS permissions. Do not grant broad Automation or Accessibility permissions to the host process unless you trust the MCP client, prompts, and scripts it will run. Review generated scripts before execution, use short timeouts for untrusted automations, and avoid running scripts against Mail, Messages, Contacts, Calendar, browsers, password managers, terminals, or cloud-sync folders without explicit approval. Knowledge-base scripts and custom local knowledge-base overrides can change the behavior of reusable script IDs; review local overrides before relying on them. Use separate macOS user accounts or test machines when experimenting with destructive file, shell, browser, or system-setting automation.After Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them. The bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes. Layer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project. The install script may copy files into Adobe application folders and may require elevated privileges on some systems. Enabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects. Use only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
Privacy notesTool calls can expose message text, timestamps, participants, phone numbers, email addresses, contact names, group chat names, chat IDs, attachment metadata, filenames, MIME types, local paths, and inline image data. Messages may contain personal, medical, legal, financial, work, customer, family, or authentication information. Fetched attachment paths and inline images can reveal private media, documents, screenshots, PDFs, audio, or video files. MCP client logs and model context may retain conversation snippets, contact matches, message-search queries, and outbound message drafts.Tool calls can expose contacts, phone numbers, email addresses, calendars, event details, reminders, message text, participants, location, routes, map queries, screenshots, camera images, audio snippets, shortcut names, and weather/location context. iMCP's README states that iMCP does not collect or store user data, but MCP clients and model providers can receive tool-call data as part of the conversation. Local logs, screenshots, approval dialogs, MCP transcripts, Claude Desktop config, and trusted-client settings may reveal private service access and personal-data context. Review every service toggle and macOS permission before enabling iMCP for personal accounts, shared machines, work devices, or regulated data.Scripts can expose local file paths, file contents, clipboard data, browser URLs and page data, email subjects, contacts, calendar events, messages, app state, system settings, shell output, and account-specific metadata. Error responses and optional debugging settings can include attempted script content, script paths, substitution logs, stderr, and execution details. The local knowledge base defaults to `~/.macos-automator/knowledge_base` when configured and may contain private automation recipes or paths. MCP clients, model providers, terminal history, and application logs may retain script inputs and outputs, including data read from local apps.Tool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths. Project contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details. The command and result files in the local bridge directory can persist recent instructions and After Effects output. MCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
Prerequisites
  • macOS with Messages configured for iMessage, SMS, or RCS delivery.
  • Python 3.10 or newer and uv for the recommended `uvx` launch path.
  • Full Disk Access granted to the terminal, Claude Desktop, Cursor, or other host application that runs the MCP server.
  • Contacts or AddressBook permission if using contact lookup.
  • macOS 15.3 or later.
  • iMCP app installed from the upstream release or Homebrew cask.
  • Claude Desktop, Claude Code, Cursor, Amp, or another MCP client that can launch the bundled stdio server.
  • macOS permissions reviewed for each enabled service.
  • macOS on the machine running the MCP server.
  • Node.js 24 or newer for the published npm package.
  • Automation permissions for the terminal, editor, or app that launches the MCP server.
  • Accessibility permissions when scripts need UI scripting, clicks, keystrokes, or System Events access.
  • Adobe After Effects 2022 or newer.
  • Node.js, npm, and a local checkout of the repository.
  • Permission to install the ScriptUI panel into the After Effects ScriptUI Panels folder.
  • After Effects scripting preferences reviewed, including whether scripts may write files and access the network.
Install
uvx mac-messages-mcp
Install the iMCP macOS app, enable only the services you need, then configure the bundled imcp-server from the app menu or your MCP client.
npx -y --package @steipete/macos-automator-mcp macos-automator-mcp
git clone https://github.com/Dakkshin/after-effects-mcp.git && cd after-effects-mcp && npm install && npm run build
Config
{
  "mcpServers": {
    "messages": {
      "command": "uvx",
      "args": [
        "mac-messages-mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "iMCP": {
      "command": "{path-to-imcp-server}"
    }
  }
}
{
  "mcpServers": {
    "macos_automator": {
      "command": "npx",
      "args": [
        "-y",
        "--package",
        "@steipete/macos-automator-mcp",
        "macos-automator-mcp"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
npm run build && npm run install-bridge
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.