mcp-server-apple-events
Enables Claude to directly read and write calendar events and reminders on macOS without manual sync, reducing friction for teams that rely on Apple ecosyste…
MCP server that gives Claude native access to Apple Reminders and Calendar on macOS through the EventKit framework. Supports full create/read/update/delete on reminders and calendar events, plus priorities, recurring reminders, location-based triggers, tags, and subtasks. Runs via npx; macOS prompts for Reminders and Calendar permissions on first use.
- Ask Claude to create calendar events from meeting notes automatically.
- Generate reminder notifications for your team's upcoming deadlines and milestones.
- Find conflicts between your calendar events and suggest better meeting times.
Enables Claude to directly read and write calendar events and reminders on macOS without manual sync, reducing friction for teams that rely on Apple ecosystem tools for scheduling and task management.
macOS-native engineering teams using Apple Calendar and Reminders for project planning and deadline tracking.
https://github.com/FradSer/mcp-server-apple-events
By FradSer
How to Get It
claude mcp add mcp-server-apple-events -- npx -y mcp-server-apple-events
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Create calendar events from meeting notes automatically
Trust Signals Auto-scanned
Data & Access
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 180 GitHub stars; 18 contributors; last commit 7d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 180 GitHub stars; 18 contributors; last commit 7d ago; license MIT.