The full MCP for Zapier
Create, edit, debug and manage your Zaps from your AI assistant. Everything, not just actions.
https://mcp.zapsmith.com/mcp
Paste it as a custom connector, sign in with Zapier, done. How to connect
phone instead of phone_number+ Phone: {{1__phone}}
Why Zapsmith
Other Zapier MCPs run actions.
Zapsmith works on your Zaps.
Zapier's own MCP lets an assistant send an email or create a row. It cannot see, build or fix the automations you already run. Zapsmith can.
| What your assistant can do | Action MCPs | Zapsmith |
|---|---|---|
| Run single app actions | ✓ | ✓ |
| List and read your Zaps, step by step | ✕ | ✓ |
| Create new Zaps | ✕ | ✓ |
| Edit steps, inputs and field mappings | ✕ | ✓ |
| Turn Zaps on and off, delete them | ✕ | ✓ |
| Read run history and find failures | ✕ | ✓ |
| Preview every change and undo it | ✕ | ✓ |
Features
Everything you do in the Zap editor, by asking
27 tools covering Zaps, steps, fields, connections, tests and run history.
Edit without fear
Targeted edits instead of rewriting whole Zaps. See the exact diff before anything changes.
Backups and undo
Every change is backed up first. Restore any version, even a Zap you deleted.
Debug failed runs
Find the runs that failed, see which step broke, and test it with live data.
Build new Zaps
Describe the workflow. Your assistant finds the apps, fills the fields and maps the data.
Your account, your keys
Sign in with Zapier's own OAuth. Tokens are encrypted, and each user only ever sees their own Zaps.
Open source
MIT licensed. Use the hosted version or run it on your own server with one Docker command.
Connect
Up and running in a minute
No API keys to copy. Your AI app handles the sign-in.
Add the server
Add https://mcp.zapsmith.com/mcp as a custom connector or remote MCP server.
Sign in with Zapier
Approve access on Zapier's own page. Your password never touches Zapsmith.
Just ask
"Why did my lead Zap fail yesterday?" "Build a Zap that posts new Stripe payments to Slack."
Claude (web and desktop)
Settings → Connectors → Add custom connector, then paste the URL.
Claude Code
claude mcp add --transport http zapsmith https://mcp.zapsmith.com/mcp
ChatGPT
Settings → Connectors → Create, then paste the URL (developer mode).
Cursor, VS Code and others
Add a remote (Streamable HTTP) MCP server with the URL. The client runs the sign-in.
Self-host
Open source. Run it anywhere.
One Node.js process and one SQLite file. Bring your own Zapier OAuth app, add a domain, and your team connects through your own server.
cp .env.example .env # add your Zapier client ID and secret docker compose up -d --build # then connect to https://your-domain.com/mcp
Questions
Is Zapsmith made by Zapier?
No. Zapsmith is an independent open-source project built on Zapier's public Workflow API. It is not affiliated with or endorsed by Zapier.
What can it change in my account?
Only what you ask your assistant to do. Every edit can be previewed first, every change is backed up, and deleting a Zap needs an explicit confirmation.
Does Zapsmith see my Zapier password?
Never. You sign in on Zapier's own page. Zapsmith receives a token that it stores encrypted and uses only for your requests.
Is there anything Zapier's API does not allow?
Yes. The API has no drafts or version history, so every saved edit goes live right away. Zapsmith makes that safe with previews, backups and one-step restore. Run history shows step status but not step error messages.
How much does it cost?
The hosted version is free while in beta. Self-hosting is free forever.
What data do you collect?
Anonymous usage data such as which tools are used and whether they succeed. Never your Zaps, their contents, or what you type. See the privacy policy.