Skip to main content
hc
Submit
mcpSource-backed
iMCP logo

iMCP MCP Server

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.

by Mattt · submitted by oktofeesh1·added 2026-06-06·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
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.

Canonical URL
https://heyclau.de/entry/mcp/imcp-mcp-server
Source URLs
https://raw.githubusercontent.com/mattt/iMCP/main/README.md, https://github.com/mattt/iMCP
Brand
iMCP
Brand domain
imcp.app
Brand asset source
brandfetch
Safety notes
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.
Privacy notes
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.
Author
Mattt
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

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

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

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

0/5 ready
Install & runtime2Review & approval2General115 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 4 privacy notes across 4 risk areas. Review closely: permissions & scopes, third-party handling.

4 areas
  • SafetyGeneraliMCP can expose highly sensitive personal macOS services to Claude through MCP tools.
  • SafetyExecution & processesCalendar, Contacts, Reminders, and Shortcuts tools can create, update, or run actions, not only read data.
  • SafetyPermissions & scopesCapture tools can take pictures, record microphone audio, and capture screenshots when the corresponding service is enabled and macOS permission is granted.
  • SafetyPermissions & scopesMessages access can read local message history after the user grants access to the Messages database.
  • SafetyGeneralThe app can add or update the iMCP entry in Claude Desktop MCP configuration while preserving other server entries.
  • SafetyGeneralEnable only the services needed for a task and do not mark clients as trusted unless you want repeated connections to bypass prompts.
  • PrivacyGeneralTool 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.
  • PrivacyThird-party handlingiMCP'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.
  • PrivacyExecution & processesLocal logs, screenshots, approval dialogs, MCP transcripts, Claude Desktop config, and trusted-client settings may reveal private service access and personal-data context.
  • PrivacyPermissions & scopesReview every service toggle and macOS permission before enabling iMCP for personal accounts, shared machines, work devices, or regulated data.

Disclosure: MIT-licensed open-source macOS app and MCP server. This entry emphasizes iMCP's personal-data permissions and bundled stdio proxy rather than treating it as a generic low-risk desktop utility.

Safety notes

  • 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.

Privacy notes

  • 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.

Prerequisites

  • 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.
  • Human approval workflow for first-time client connections and trusted-client settings.

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 open-source macOS app and MCP server. This entry emphasizes iMCP's personal-data permissions and bundled stdio proxy rather than treating it as a generic low-risk desktop utility.
Full copyable content
{
  "mcpServers": {
    "iMCP": {
      "command": "{path-to-imcp-server}"
    }
  }
}

About this resource

Content

iMCP is a macOS app that bundles a stdio MCP executable called imcp-server. The app handles service toggles, macOS permission prompts, and client approval, while the CLI proxies MCP traffic between stdin/stdout and the local app over a local-only Bonjour-discovered connection.

Use it when Claude needs narrowly scoped access to personal macOS services such as Calendar, Contacts, Messages, Location, Maps, Reminders, capture tools, Shortcuts, utilities, or Weather. Because these tools can expose personal data and some tools can write or run actions, enable only the services required for a specific workflow.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, CLI proxy source, server controller, Claude Desktop integration source, and permission-sensitive service source files for current behavior.

Features

  • Bundle a macOS menu-bar app with a stdio MCP executable.
  • Toggle individual macOS services on or off.
  • Require macOS permission prompts for sensitive services.
  • Approve or trust connecting MCP clients from the app.
  • Read Calendar, Contacts, Messages, Location, Maps, Reminders, and Weather data when the corresponding service is enabled.
  • Create or update Calendar events, Contacts, and Reminders.
  • Take pictures, record audio, and take screenshots through capture tools.
  • Run Shortcuts when that service is enabled.
  • Add or update the iMCP server entry in Claude Desktop configuration.
  • Return structured JSON-LD style results for many tool calls.

Installation

Install the iMCP macOS app from the upstream release or Homebrew cask, then open the menu-bar app and enable only the services you want Claude to access.

Use the app's Claude Desktop configuration action, or manually configure an MCP client with the bundled server command:

{
  "mcpServers": {
    "iMCP": {
      "command": "{path-to-imcp-server}"
    }
  }
}

After connecting, approve the client in iMCP before using the tools. Avoid trusting a client permanently until you are comfortable with the service set it can access.

Use Cases

  • Ask Claude to summarize upcoming events from an approved calendar.
  • Search recent Messages with specific participants and date ranges.
  • Look up contact details before drafting a reply.
  • Create a reminder or calendar event after reviewing the proposed fields.
  • Ask for route, ETA, place, weather, or location context.
  • Capture a screenshot or image only when visual context is needed.
  • Run a reviewed local Shortcut as part of a personal workflow.

Safety and Privacy

iMCP is powerful because it connects Claude to personal macOS data. That also makes it high-trust software. Start with all optional services disabled, enable one service at a time, and test with low-sensitivity data before using it for private calendars, personal messages, work contacts, location data, screenshots, audio, or camera capture.

Pay special attention to write-capable tools. Creating reminders, calendar events, contacts, and running Shortcuts can change local state or trigger other automation. Review the exact tool call before approving it, and use client trust settings sparingly.

Duplicate Check

No mattt/iMCP, iMCP MCP Server, or matching iMCP source URL entry was found in content/mcp or README.md. Existing Mac Messages and Calendar entries cover narrower standalone projects; this entry covers iMCP's app-mediated, multi-service macOS MCP server.

#macos#personal-data#desktop#calendar#messages

Source citations

Add this badge to your README

Show that iMCP 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/imcp-mcp-server.svg)](https://heyclau.de/entry/mcp/imcp-mcp-server)

How it compares

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

Field
iMCP logoiMCP MCP Server

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
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.

Open dossier
Keeper.sh logoKeeper.sh MCP Server

Self-hostable calendar MCP service for Keeper.sh that lets Claude list calendars and accounts, read events, create or update events, delete events, respond to invites, and retrieve iCal feed URLs through Keeper's API.

Open dossier
macOS Automator MCP

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
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
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—Keeper.sh logoKeeper.sh—
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorMatttCarter LasalleridafkihPeter Steinberger
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓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.✓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.✓Keeper's MCP tools can read calendar data and perform write operations including event creation, event updates, event deletion, and RSVP changes. The MCP handler requires an authenticated bearer token and checks for the Keeper MCP read scope before exposing tools. Tool calls proxy to Keeper API endpoints with the caller's bearer token, so the MCP client inherits the user's connected calendar permissions. Start by listing calendars and reading bounded date ranges; require human confirmation before modifying or deleting events. Review Google, Microsoft, iCloud, CalDAV, ICS, and self-hosted calendar account permissions before exposing them to an agent.✓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.
Privacy notes✓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.✓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.✓Calendar events can expose titles, descriptions, locations, free/busy status, account names, provider names, calendar names, calendar URLs, and iCal feed URLs. OAuth tokens, CalDAV credentials, session tokens, bearer tokens, auth secrets, encryption keys, database URLs, and MCP URLs are sensitive deployment data. Keeper stores and syncs calendar data across connected providers; logs, MCP transcripts, API responses, and monitoring traces can include private schedule details. Redact event ids, calendar ids, account names, feed URLs, bearer tokens, event text, locations, and provider details before sharing debug output.✓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.
Prerequisites
  • 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 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.
  • Self-hosted or hosted Keeper.sh deployment with the MCP service available.
  • Keeper API, database, auth secret, and MCP public URL configured.
  • Authorized Keeper bearer token with the required MCP read scope.
  • Connected calendar accounts and calendars reviewed for read and write access.
  • 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.
Install
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.
uvx mac-messages-mcp
Deploy Keeper.sh with the MCP service enabled, configure `MCP_PUBLIC_URL`, and connect an MCP client to the Keeper MCP endpoint with an authorized bearer token.
npx -y --package @steipete/macos-automator-mcp macos-automator-mcp
Config
{
  "mcpServers": {
    "iMCP": {
      "command": "{path-to-imcp-server}"
    }
  }
}
{
  "mcpServers": {
    "messages": {
      "command": "uvx",
      "args": [
        "mac-messages-mcp"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
BETTER_AUTH_URL=https://<keeper-host>
MCP_PUBLIC_URL=https://<keeper-host>/mcp
MCP_PORT=3002
{
  "mcpServers": {
    "macos_automator": {
      "command": "npx",
      "args": [
        "-y",
        "--package",
        "@steipete/macos-automator-mcp",
        "macos-automator-mcp"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Claude Code Desktop Parallel Sessions Workflow

Coordinate parallel Claude Code Desktop sessions with clear ownership rules.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Scheduled Tasks In Claude Code Desktop

Schedule recurring Claude Code maintenance from Desktop with scoped tasks and run review.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

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