A support team using Claude and engineers using Cursor no longer need separate Zapier MCP servers for the same app connections. Zapier’s October 20 announcement introduces multiple clients on one server, sharing its configured apps and actions.
Tool calls from those clients appear in one history. That puts the record of an action in the same place whether the request started in a support assistant or a coding tool. Existing account and workspace restrictions still apply.
The server’s mode follows every client
In managed mode, the server owner selects permitted actions and can lock a field, such as the Slack channel a message targets. Skills have a separate condition: they work in agentic mode, while managed servers share apps and actions without skills.
Zapier says multi-client servers are available in every plan. Adding a client requires Owner or Editor access to the server. A client can connect to only one server at a time, so moving it also changes the tools and mode it inherits.
For a team consolidating connections, start with the server whose action set already matches the intended work. Review its mode before moving clients: sharing a server also means sharing that configuration, not just reducing setup steps.
