For the complete documentation index, see llms.txt. This page is also available as Markdown.

14. Zapier MCP Server

Think of Zapier as a universal remote control for all your favorite apps and online services , things like Gmail, Google Sheets, Slack, and hundreds more. Normally, Zapier lets you create automated workflows that connect different apps together, so they can "talk" to each other without you having to do anything manually.

Now, the Zapier MCP Server takes this one step further: it acts as a bridge between an AI assistant and all those apps and automations you've set up in Zapier.

This MCP is useful for:

  • Integrating Zapier into your Agent

  • Automating processes across different applications

  • Connecting services that don't have dedicated MCPs

Configuration parameters

Parameter
Required
Description

zapier_webhook_url

Yes

URL of the Zapier webhook that receives requests (e.g. https://hooks.zapier.com/hooks/catch/.../).

automation_name

No

Descriptive name of the automation, used in the agent's instructions.

supergateway_args

No

Advanced extra arguments for the connection. Rarely needed.

auth_token

No

Authentication token for the Zapier webhook, if it is protected.

Custom parameters

  • timeout: maximum time for a request (seconds)

  • retries: number of retries in case of failure

  • retryDelay: pause between retries (ms)

  • headers: custom HTTP headers to send

Best practices

When configuring MCPs for your Agent, keep these tips in mind:

  • Security: never share API keys, passwords, or authentication tokens. Always use secure connections (HTTPS, SSL/TLS) when available

  • Testing: always test the MCP configuration in a test environment before using it in production

  • Limits: check the rate limits (requests per minute/hour) of external services to avoid getting blocked

  • Errors: implement appropriate error handling in the Agent's instructions to deal with potential connection issues

  • Documentation: always consult the official documentation of external services to understand available features and configuration requirements

  • Custom parameters: use custom parameters in JSON format for advanced configurations, but always verify they're supported by the specific MCP

Last updated