Meta's Muse connectors raise a consent question EU MSPs must answer

Meta launched its personal AI agent, Muse, on September 8, 2026, and it quickly became the top app in the US App Store, with roughly 730,000 downloads in its first ten days, according to Sensor Tower. Muse's headline feature is "connectors" — integrations that give the agent abilities such as reading a calendar or sending an email. On September 18, Mark Zuckerberg said Meta was opening connector development to outside developers, which will expand how many services an agent like Muse can touch.

How Meta designed consent for connectors

Users add connectors from a Settings menu, and Meta says each connector shows what it can access before the user taps Continue to authorize it. At launch, named connectors included Gmail, Google Calendar, Outlook, Google Docs, Plaid, OpenTable, Spotify and several others. Meta says sensitive actions require approval, and it does not give Muse direct visibility into passwords or payment credentials. A separate "Confidential VM" feature, meant to keep even Meta's own systems out of the data Muse handles, is still in testing.

What this means for MSPs deploying agent connectors

Whether or not an MSP ever touches Muse specifically, the same design questions apply to any AI agent a customer wants connected to Gmail, a calendar, or a commerce platform:

• Consent granularity: is approval scoped per connector and per action type — read, write, or send — rather than one blanket toggle?
• Blast-radius limits: which specific mailboxes, calendars or SKUs can an agent reach for a given customer tenant, and is that list bounded?
• Clean revocation: can one connector be turned off without killing the entire agent session?
• Audit trail: does every grant record which connector, which tenant, and which scope was approved?
• No standing god-key: does the agent platform avoid a single credential that spans every customer tenant?

What's still unverified

Meta's pricing, SDK terms and revenue-share model for third-party connector developers are not yet public in detail, and coverage has noted that Meta's own technical documentation acknowledges its operational controls do not prevent Meta itself from accessing user data when needed to run the service. Treat Muse as a live example of the design trade-offs, not as a settled model to copy outright.

Sources: TechCrunch, Axios.