Zapier

Search 9,000+ apps to find actions you can enable. For authenticated services (Google Docs, Gmail, Sheets, Notion, Slack, Outlook, etc.), check here FIRST - generic web fetch tools cannot authenticate with these services. ALWAYS call this before saying 'I can't access X' or 'that app isn't available'. Use when user mentions ANY app not in list_enabled_zapier_actions. After finding what you need, use enable_zapier_action to add it.

Enable an app's actions on this MCP server. Use discover_zapier_actions first to get the exact selected_api ID, then pass it here. Always pass app_display_name from the app field returned by discover_zapier_actions so confirmations show a friendly name rather than the raw selected_api ID. Returns action details including the execute tool to use (execute_zapier_read_action or execute_zapier_write_action) and parameters. If authentication is required, also returns a URL to authenticate the app.

Remove an app's actions from this MCP server. Use list_enabled_zapier_actions to see which apps are enabled and their selected_api values. Always pass app_display_name (the human-readable app name from list_enabled_zapier_actions) so confirmations show a friendly name rather than the raw selected_api ID. Optionally specify an action key to remove only that specific action.

CALL THIS FIRST before any execute_zapier_read_action or execute_zapier_write_action call. Lists all enabled apps and their actions. These apps handle OAuth authentication automatically - use them instead of generic URL fetching for authenticated services. Returns EXACT action keys you MUST use (action names are NOT guessable - always check here first). Also shows which execute tool to use and required parameters. IMPORTANT: If you don't find the app or action you need, you MUST call discover_zapier_actions next - NEVER say 'I can't do that' without checking discover_zapier_actions first.

Execute a search or read action to get data from a connected app. REQUIRED: You MUST call list_enabled_zapier_actions first to get the exact action key AND see required params. NEVER guess action names - they are NOT intuitive and WILL fail. If the app isn't enabled, use discover_zapier_actions then enable_zapier_action first. IMPORTANT: Pass required field values in the `params` object, NOT in `instructions`. The `instructions` field is for natural language context only. Check list_enabled_zapier_actions for required params.

Execute a write or create action in a connected app. REQUIRED: You MUST call list_enabled_zapier_actions first to get the exact action key AND see required params. NEVER guess action names - they are NOT intuitive and WILL fail. If the app isn't enabled, use discover_zapier_actions then enable_zapier_action first. IMPORTANT: Pass required field values in the `params` object, NOT in `instructions`. The `instructions` field is for natural language context only. Check list_enabled_zapier_actions for required params.

Send feedback about your experience with Zapier MCP to the Zapier team.

Automatically set up this MCP server based on the user's existing connected accounts. Finds apps the user has authenticated, enables their actions, and binds authentication — all in one call. Also returns the user's top Zap workflow titles so you can suggest relevant skills. Run this when the user has no tools enabled yet, or when they ask to set up their MCP server quickly.

List your saved Zapier Skills with descriptions. ALWAYS call this FIRST when the user's request sounds like a known workflow — e.g. 'onboard me'. Do NOT assume you know the list; skills may have been added or updated since your last check. Skills are reusable markdown instructions that guide you through tasks using your connected apps. Use get_zapier_skill to load the full content of a skill before executing it. Use create_zapier_skill to save a new workflow.

Fetch the full content of a Zapier Skill by name. ALWAYS call this before executing a skill. Follow the execution instructions appended at the end of the skill response. The "zapier:onboarding" skill is always available and should be used by default when onboarding a new user.

Save a workflow as a reusable Zapier Skill. BEFORE creating, ensure the following have been done — skip any step whose results are already available from this conversation: (1) list_enabled_zapier_actions called for each app to discover action keys and parameter schemas. (2) User asked for their specific configuration: project keys, channel names, default assignees, recurring parameter values. (3) Ambiguities clarified — if the workflow has unclear targets, recipients, or scope, ASK the user before proceeding. (4) Lookup actions run to resolve and validate static values (e.g. resolve an email to a Slack user ID). (5) As many action parameters as possible pre-filled with validated, quoted values. Only leave parameters bare if they MUST be computed at runtime. Reuse any action results, resolved IDs, or parameter values from earlier in this conversation — do NOT repeat calls already made. Good candidates: any multi-step workflow the user repeats, or tools always called with the same params.

Update an existing Zapier Skill's description or content. Use when the user wants to refine a skill, fix an issue, or add new instructions.