Agents in Superconductor can now use the apps you connect through Zapier.
We build first-class integrations for the tools that show up in most engineering workflows. But every team also has a long tail of its own: a CRM, a support inbox, a scheduling tool, an internal spreadsheet that one team quietly depends on. Zapier MCP covers that tail. You choose which apps and actions to expose, and agents get those and nothing more.
One of our favorite use cases so far comes from universities. A professor can ask an agent to write a recommendation letter for a student, and with Gmail connected through Zapier the agent reads the email threads about that student, drafts the letter, and returns it to the Superconductor chat as DOCX and Markdown artifacts.
Some other use cases:
- Look up the account behind a bug report in your CRM or support tool before the agent writes the fix
- Post the outcome of an implementation into whichever tracker or channel your team actually watches
- Pull in a spec that lives in a spreadsheet or an internal wiki and never made it into the ticket
Access stays personal. Everyone creates their own Zapier server and adds their own token, so an agent only ever reaches the app connections of the person it is working with.
To turn it on, create a server at Zapier MCP, enable Zapier under Project Settings -> Skills and MCPs, and add your token in Workspace Settings -> Personal Settings.
Zapier joins everything else agents can reach from Superconductor. Check out our full list of supported Skills and MCP servers.
Which MCP or integration should we support next? Let us know!