Zapier MCP server
Zapier publishes its own remote MCP server. Govern it with Anlyon: adopt only the tools you choose, and have a person approve the ones that delete data or can't be undone. Your agent never holds your Zapier credentials.
- endpoint
- https://mcp.zapier.com/api/v1/connect
- registry name
- com.zapier/mcp
- published by
- zapier.com
- verified
- domain, by the MCP Registry
- transport
- Streamable HTTP
Tool report on anlyon.dev
- 1.Add the serverPress Govern it. The console opens with mcp.zapier.com filled in and reads what sign-in it needs. Nothing is saved yet.
- 2.Connect ZapierConnect the way the server asks: sign in, or add a key. The credential stays in Anlyon's vault, and your agent never holds it.
- 3.Adopt what you chooseEach tool you adopt becomes an action with the approval you set. A tool you skip can't be called.
Which tools need a person? Approve the ones you can't take back.
anlyon.dev classes each of Zapier's tools by what it can do. The console shows the same classes when you add the server.
- Require approval for any Zapier tool that deletes or cancels something, and for any that sends, pays, publishes or merges: those can't be taken back.
- Put the tools that create or change things under a limit, or approval where a mistake is costly.
- Let the tools that only read through.
Questions. Zapier's official MCP server.
It is Zapier's own server: the MCP Registry verified its publisher as the domain zapier.com, and its endpoint, mcp.zapier.com, is on Zapier's domain. What your agent can do with it depends on which tools it may call. With Anlyon it reaches only the tools you adopt, and the ones that delete data or can't be undone can wait for a person's approval.
anlyon.dev lists each of Zapier's tools with what it can do, including the ones that delete or cancel things. In Anlyon none of them can be called until you adopt it, and an adopted one can wait for a person's approval.
https://mcp.zapier.com/api/v1/connect. Its name in the MCP Registry is com.zapier/mcp.