Zapier MCP Server
The Zapier MCP server lets your AI agents discover and execute automated actions across Zapier's ecosystem of 7,000+ connected apps. Agents can check available connections, browse allowlisted actions, execute automations, and monitor the results — all within a governed framework that restricts which actions can be performed.
Capabilities
| Tool | What It Does |
|---|---|
| Health check | Verify that the Zapier API connection is working |
| List connections | List the user's Zapier app connections |
| Get connection status | Check the status of a specific Zapier connection |
| List actions | Browse available actions from the allowlist |
| Get action schema | View the input/output schema for a specific action |
| Execute action | Run an allowlisted action (for example, send a Slack message, create a Trello card) |
| List tool runs | View recent action execution history |
| Get tool run | Get details about a specific action execution |
How Zapier Actions Work
Zapier actions represent specific operations in external apps — for example, "Send a Slack message", "Create a Google Sheets row", or "Add a Trello card". The Zapier MCP server provides a curated, governed way for agents to use these actions:
- Discovery: The agent can list available connections and actions.
- Schema inspection: Before executing, the agent can retrieve the expected input/output format for an action.
- Execution: The agent executes the action with the appropriate input parameters.
- Monitoring: The agent can check execution results and history.
📝 Note: Action execution is governed by an allowlist. Only actions that have been explicitly permitted by your organization's configuration can be executed. This prevents agents from performing unauthorized operations.
OAuth Setup
The Zapier MCP server uses OAuth to authenticate on behalf of each user.
Step 1: Get Zapier OAuth Credentials
Contact your Zapier account administrator or refer to the Zapier Platform documentation for instructions on obtaining OAuth credentials for your integration.
Step 2: Configure in Devs.ai
- Navigate to Organization > Connectors in Devs.ai.
- Find the Zapier template and click Enable.
- Select OAuth as the authentication type.
- Enter your Client ID and Client Secret.
- Select the tools you want to make available.
- Click Save.
Required Scopes
| Scope | What It Enables |
|---|---|
actions:read | List and inspect available actions |
actions:execute | Execute allowlisted actions |
connections:read | List and check connection status |
runs:read | View action execution history |
OAuth Configuration Reference
| Field | Value |
|---|---|
| Authorization URL | https://zapier.com/oauth/authorize |
| Scopes | actions:read actions:execute connections:read runs:read |
| Scopes Parameter Name | scope |
Security and Governance
The Zapier integration includes several built-in safety mechanisms:
- Allowlist enforcement: Only actions explicitly listed in the organization's allowlist can be executed. If no actions are allowlisted, execution is blocked entirely.
- Dry run support: Actions can be tested without actually executing them, allowing agents to verify inputs before committing.
- Output redaction: Sensitive keys in action outputs can be automatically redacted.
- Per-user authentication: Each user authenticates with their own Zapier account, so actions run within that user's permissions and connected apps.