Permissions
LMCP uses macOS's standard privacy system (TCC): each feature asks for exactly the permission it needs, the first time you use it. You choose what to enable, and you can revoke anything in System Settings.
Which permission unlocks what
| macOS permission | What it enables in LMCP |
|---|---|
| Calendars | Read & create events, check availability |
| Contacts | Search people, look up emails & phone numbers |
| Reminders | Read, create and complete reminders / To Do tasks |
| Full Disk Access | Mail bodies & attachments, iMessage history, Teams/Slack/WhatsApp/Signal local caches, file search |
| Automation (Apple Events) | Acting in apps: send email via Mail, create Notes, drive Safari, OmniFocus, Messages |
| Accessibility | GUI automation — click, type, menus, windows in any app |
| Screen Recording | Screenshots & screen recordings (capture tools) |
Nothing is requested up front — if you never use a feature, its permission is never asked for. Grants persist across updates (the app is signed with a stable Developer ID).
Granting a permission
When your AI first uses a feature, macOS shows its standard prompt (“LMCP would like to access…”). Click Allow. Full Disk Access is the one exception macOS makes you grant manually: System Settings → Privacy & Security → Full Disk Access → enable Local MCP (the app guides you there when needed).
Revoking a permission
System Settings → Privacy & Security → pick the category (Calendars, Full Disk Access, Automation…) → toggle Local MCP off. The relevant tools stop working immediately and tell the AI why.
What this means for privacy
- All reads happen on your Mac; no content is uploaded anywhere.
- Anything the AI sends (email, message) shows a preview and requires your confirmation.
- The optional Cloud Relay is off by default; when on, data transits encrypted and is never stored server-side.
See the full privacy policy and GDPR guide.