I’m attempting to add Claude to my MCP server on Zapier, but the permissions it requests are quite concerning. It wants to access my entire Zapier account, including third-party login info for all connected tools, view all tools I’ve activated, and run any enabled tools while saving the results. This feels excessive. I’m worried about how my privacy is affected after granting these permissions. AI can be unpredictable, so I’m reluctant to allow such extensive access. Has anyone faced this issue? Are all these permissions truly necessary, or can I restrict Claude’s access somehow?
Yeah, you need those broad permissions for MCP servers to work with Zapier’s API - no way around it. I had the same worries when I set this up six months ago. What made me feel better was realizing Claude won’t just run wild with your Zaps. It asks for approval before triggering anything, and you can check Zapier’s activity logs to see exactly what it did and when. I’d start with read-only stuff first to get a feel for it. I actually turned off my sensitive Zaps while I was learning how Claude works with the system. The permissions look scary because Zapier’s API is all-or-nothing, but Claude still needs your OK and follows what you tell it to do.
Had the same issue with Claude’s MCP setup last month. Those broad permissions are standard across most AI-MCP connections, not just Claude’s fault. Here’s what worked for me: I made a separate Zapier account just for AI stuff and only added the tools I actually wanted Claude touching. Even with full permissions, it can only mess with those specific services. You can kill access anytime in Zapier’s connected apps if things get weird. Just be picky about what tools you put on that second account. More setup work, but way less stress when the AI does something unexpected.
Same here - the permissions scared me at first, but it’s actually fine after using it a few weeks. Claude doesn’t go rogue with your Zapier stuff. You still have to confirm most actions anyway. I’d disable your riskiest zaps while testing though, just so you can see how it works without worrying about breaking something important.