Framer AI AgentsDesign and publish professional sites with AI
Macuse
Give Your AI Superpowers on macOS
130 followers
Give Your AI Superpowers on macOS
130 followers
Macuse is a native macOS app that connects Claude, Codex, Cursor, Raycast, and any MCP-compatible AI client to your Mac apps. It gives AI assistants local access to Calendar, Mail, Notes, Reminders, Messages, and real app control through Computer Use.
The 'every connection requires approval and can be revoked' line is what matters most to me here, but how granular is that approval? Is it per-app (grant Calendar but withhold Messages/Mail), or one grant per client that then covers everything Macuse can touch? And for outbound actions like sending a Message or letting a Mail draft actually go out, is that gated separately each time, or does the initial connection approval cover silent sends?
mcp calls and computer-use have very different blast radii — reading a calendar is a scopable tool call, but 'real app control' via computer use is an unscoped click that does whatever the frontmost app can. the gate between those two is the hard part
Does Computer Use actually click around in your real apps without sandbox issues, or do you need to grant a bunch of accessibility permissions first?
How does Macuse handle permissions when giving an AI client access to Mail and Messages, and is there any sandboxing or audit log so I can see exactly what got read or sent?
Finally something that lets Claude actually touch my Mac apps without me copy-pasting between windows. Calendar and Mail worked right away once I granted the permissions, and the MCP setup was painless.
Finally a clean way to let Claude actually read my Mail and Calendar without weird workarounds. The MCP setup was painless and everything stayed local.
Finally a clean way to let Claude actually touch my Mac apps without weird workarounds. Setup with Calendar and Mail took like two minutes and the permissions prompt felt transparent instead of sketchy.