Cloud boundary
MCP integrations operate on cloud-backed data. They do not turn device-only state into hosted state.
| Data or behavior | Integration boundary |
|---|---|
| Free personal data stored only on a device | Not visible to hosted MCP tools |
| Cloud-backed Tasks and Lists | Visible only when the exact connection, scope, ownership, membership, and entitlement checks pass |
| Shared Lists | Hosted by the owner’s entitlement; membership grants only the access defined by the collaboration model |
| Attachment metadata | Available only through an authorized MCP tool |
| Attachment bytes | Delegated with short-lived signed URLs when supported; never flow through MCP messages |
| Local reminders and notifications | Remain device behavior unless a current MCP tool explicitly exposes related cloud state |
| Geofence monitoring | Remains device behavior |
Tool responses are intentionally bounded. Access to Notes, comments, collaborator information, settings, precise location, attachments, and activity requires the corresponding scope and the tool’s own authorization checks. OAuth credentials are never tool content.
Webhook operational caps
Section titled “Webhook operational caps”These are operational limits, not a plan feature: they may change as usage patterns become clearer. Full behavior for each row is described on the webhooks page.
| Cap | Current value | Scope |
|---|---|---|
| Subscriptions per connection | 5 | The connection that created the subscription |
| Subscriptions per account | 20 | The account, across every connection |
| Logical delivery allowance | 50,000 | Rolling 30 days, per account; automatic retries are free, replays count |
| Hidden HTTP-attempt ceiling | 6,000 | Rolling hour, per account; defers the next attempt rather than failing the delivery |