Zapier

MCP servers, individual app-action tools, connected app accounts, configured action fields, connection tokens, server members and roles, tool-call history, and Zapier plan tasks.

Read behavior is not a universal Zapier dataset: it consists of the search, find, lookup, or retrieval actions that the server owner explicitly adds and authenticates for particular app accounts.

Write behavior consists of explicitly added app actions such as sending messages, creating rows or events, and updating records. Each tool maps to one connected-app action; multi-step outcomes require multiple calls.

The server owner authenticates each app tool and is the only person whose AI client can connect to and execute the server. Editors can add or remove tools but cannot authenticate or change account connections; View only members can inspect tools and history.

Server roles control catalog oversight, while tool authentication remains with the owner. Zapier records timestamp, tool name, AI instructions, field values, and output in History. Connection tokens can be rotated to invalidate the prior token immediately.

Each successful external-app tool call consumes two Zapier tasks; failed configuration or authentication calls do not. Calls stop when the plan task allowance is exhausted. Server and tool counts and per-session calls are not capped, but connected apps can impose their own rate limits. Server sharing is limited to Team and Enterprise accounts.