Zapier MCP

Zapier MCP connects agents to the apps and actions you choose in Zapier. Each teammate creates their own server and token, so their connected apps remain personal to their agent runs.

Setup

Zapier MCP is enabled per project, but each teammate connects their own token.

1. Go to Zapier MCP and create a server.
2. Select Other as the agent type.
3. Add the apps and actions you want agents to use.
4. Open the Connect tab and generate a token.
5. In Superconductor, go to Project Settings -> Skills and MCPs and enable Zapier.
6. Add your token under Workspace Settings -> Personal Settings.

Your token is stored encrypted, saved only to your membership in the workspace, and passed to agents only when a project enables Zapier MCP.

Whose token gets used

Agents use the Zapier token of the person a run belongs to, not the person viewing it:

• For an implementation you launch, agents use your token.
• For runs started automatically — such as from an automation, Slack, GitHub, or email triage — agents use the token of the person who created the ticket.

Your token is never used for a teammate's runs, and theirs is never used for yours. If the relevant person hasn't added a Zapier token, the run proceeds without Zapier access.

When to use it

Enable Zapier MCP when agents need to work with apps that do not have a dedicated Superconductor integration. Only add the apps and actions you want agents to access.