MCP.Market

Fruit Forwarder MCP server

by pdfowler·io.github.pdfowler/fruit-forwarder·v0.1.0
No reviews yet

Scoped local MCP access to Apple Reminders and read-only Calendar data via macOS EventKit.

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Fruit Forwarder MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Fruit Forwarder MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 37 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Fruit Forwarder MCP compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 53% of 1,299 Productivity servers

Install Fruit Forwarder MCP in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Fruit Forwarder MCP repository's README, as published. We do not edit it. Read it on GitHub

Fruit Forwarder

A local macOS bridge between Apple Reminders/Calendar and Home Assistant. It uses Apple's EventKit API for reads and writes, exposes a small stdio MCP server, and pushes allowlisted data to Home Assistant.

Early release. Reminders and read-only calendars support HA and local MCP (see calendar setup). Background EventKit permission and reboot recovery still need validation; see the release roadmap. Start with the complete setup guide for Home Assistant and local MCP configuration. Standard Lovelace examples are in docs/dashboard-examples.md. See the compatibility matrix for the current support claim and architecture decisions for the monorepo and trust-boundary choices. For issue-reporting boundaries and redaction guidance, see SUPPORT.md. The detailed threat model and security limitations are in SECURITY.md. Third-party attribution is recorded in THIRDPARTYNOTICES.md. Release history is tracked in CHANGELOG.md. The release gate is tracked in docs/acceptance-evidence.md. Mutation and recovery semantics are documented in docs/command-lifecycle.md. Reminder field support and update-preservation rules are documented in docs/reminder-semantics.md. Home Assistant's diagnostics download reports only redacted operational counts and timestamps; it excludes credentials and household contents.

Security boundary

and macOS Reminders permission.

  • Apple credentials never leave macOS. EventKit uses the Mac user's signed-in accounts

hold a Home Assistant long-lived access token.

  • The bridge makes outbound HTTPS requests to one Home Assistant webhook. It does not

list IDs for reads and writes.

  • The webhook uses a random 256-bit path token and is registered local_only.
  • Both HA and the bridge enforce a reminder-list allowlist. The bridge uses exact EventKit

operations are intentionally absent.

  • HA and MCP offer create, edit, complete, and reopen. Delete and list-management

independently available.

  • MCP can expose only read tools with "mcpreadonly": true; HA editing is

LaunchAgent environment, repository, or JSON configuration.

  • The webhook token is stored in the macOS login Keychain. It is not in the
  • Logs contain counts, command IDs, and errors—not reminder titles or notes.

Components

EventKit API.

  • eventkit-helper: a small native Swift helper using only Apple's public

stdio MCP entrypoint. It invokes the native helper directly with a 30-second timeout; macOS enforces Reminders access for the responsible application.

  • cmd/icloud-reminders-bridge: discovery, pairing, daemon, one-shot sync, and

entities and the durable command queue.

  • homeassistant/customcomponents/icloudreminders_bridge: push-driven HA todo
  • deployment: a user LaunchAgent for the Mac.

Quick start

  1. Build and install on a Mac signed in to the iCloud account that owns the lists:
./scripts/install-macos.sh --install-only
  1. Grant Reminders access when macOS prompts. Discover exact list IDs:
~/Library/Application\ Support/icloud-reminders-bridge/bin/icloud-reminders-bridge discover

you want to expose. Run pair to create a persistent bearer token and configure the Home Assistant custom integration with that token and the same list IDs.

  1. Edit ~/.config/icloud-reminders-bridge/config.json, adding only the lists
  1. Start the per-user LaunchAgent:
./scripts/install-macos.sh

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-15downgradeA → Bscore 80

Fruit Forwarder MCP: common questions

Is Fruit Forwarder MCP server safe?
Mostly: it is graded B (80/100). Read the Fruit Forwarder MCP safety report
Does Fruit Forwarder MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Fruit Forwarder MCP maintained?
The last commit was 57 days ago (2026-09-08). The latest release is v0.1.0.
What can I use instead of Fruit Forwarder MCP?
Servers from other publishers that do the same job: iCloud MCP server, Apple Calendar MCP server and DocsAgent — Zotero, Obsidian & Apple Notes MCP Server.

Alternatives to Fruit Forwarder MCP

Same job from other publishers: the closest match first, then the best rated.