Sets up and diagnoses Zapier MCP: branches to healthy summaries, auth reconnects, fresh onboarding, or server config help. Use for getting started, troubleshooting connections, adding tools.
From zapiernpx claudepluginhub zapier/zapier-mcp --plugin zapierThis skill uses the workspace's default tool permissions.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Check whether any Zapier MCP tools are available, then branch based on what comes back.
Try calling get_configuration_url or any Zapier tool. The result determines which branch to follow:
| Result | Branch |
|---|---|
Zapier action tools are available (e.g., gmail_send_email) | Healthy |
Only get_configuration_url is available (no action tools) | Fresh install |
| Fails with auth/401 error | Auth broken |
| No Zapier tools available at all (server not connected) | Not connected |
The server is connected and has action tools configured. Show a summary and offer next steps.
app_action_name (e.g., slack_send_channel_message, gmail_find_email). Identify the app from the tool description (e.g., "Send a Slack channel message" → Slack)."Your Zapier MCP is connected with [N] tools across [app list]:
slack_send_channel_message, slack_find_message, slack_get_messagegmail_find_email, gmail_send_emailgoogle_calendar_find_events, google_calendar_create_eventEverything's working. What would you like to do?"
get_configuration_url and direct the user thereThe server exists in the config but authentication has expired or is invalid.
"Your Zapier MCP server is configured but the connection is broken (authentication expired).
Sign in, find your server, and re-authenticate. Come back and say done when you're finished."
The Zapier MCP server is installed via the plugin but hasn't been authenticated yet. This is the most common state on a fresh install — zero Zapier tools are visible because the server hasn't been connected.
Tell the user the Zapier plugin is installed but needs to be connected first.
Guide them based on their client:
Detect which client is in use from the environment or conversation context. If unclear, give the generic instructions.
Explain that connecting will open the Zapier sign-in flow at mcp.zapier.com where they'll authenticate their account.
Wait for the user to confirm ("done").
Re-diagnose by checking available Zapier MCP tools. Proceed to the appropriate branch — most likely Fresh install (server connected, no action tools yet).
The server is connected but has no action tools. The user needs to add actions through the web UI.
Don't ask "what apps do you use?" Start with what they're trying to accomplish.
"You're connected but don't have any tools set up yet. Let's add some."
Call get_configuration_url and share the returned URL so the user can go directly to their server's tool config page.
Then help them pick what to add based on their workflow:
Starter kits by workflow:
| Workflow | Apps | Why these |
|---|---|---|
| Dev workflow | Jira + GitLab + Slack + Google Docs | Issue tracking, code review, team comms, documentation |
| PM workflow | Jira + Slack + Google Docs + Google Calendar + Notion | Planning, updates, writing, scheduling, knowledge base |
| Sales workflow | HubSpot + Gmail + Google Calendar + Slack | CRM, outreach, scheduling, team updates |
| Marketing workflow | Google Sheets + Slack + Notion + Gmail | Data, coordination, content, campaigns |
| General productivity | Gmail + Google Calendar + Slack + Google Docs + Google Sheets | The essentials for anyone |
"Pick a starter kit, or tell me what you're working on and I'll suggest the right tools."
Recommend specific actions the user should add for each app in the web UI. Aim for 2-4 actions per app: one or two search actions and one or two write actions.
Recommended starters by app:
| App | Search actions | Write actions |
|---|---|---|
| Slack | Find Message, Get Message | Send Channel Message |
| Gmail | Find Email | Send Email, Create Draft |
| Google Calendar | Find Events | Create Detailed Event |
| Google Docs | Get Document Content | Create Document |
| Google Sheets | Get Data Range, Lookup Row | Add Row |
| Jira | Find Issue by Key, Find Issues via JQL | Create Issue |
| Linear | Find Issue | Create Issue |
| GitLab | Find Merge Requests | (read-heavy by nature) |
| GitHub | Find Issue, Find Pull Request | Create Issue |
| HubSpot | Find Contact, Find Company | Create Contact |
| Notion | Find Page, Find Database Item | Create Page |
| Zoom | Find Meeting | (read-heavy) |
| Coda | Find Row | Create Row |
| Airtable | Find Record | Create Record |
Tell the user which actions to add for their chosen apps, then wait for them to configure and authenticate everything in the web UI.
"Add those actions and connect your app accounts in the Zapier dashboard. Come back and say done when you're finished."
After the user confirms, check the available Zapier MCP tools to see what was added. If new action tools appeared, show a summary. If nothing changed, the user may need to reload their client (see "Reload instructions by client" below).
Once everything is connected:
"Want me to create a tools profile? It teaches your AI exactly when and how to use each of these tools in future conversations."
If yes, follow the create-my-tools-profile skill.
| Client | Config file location | Scope |
|---|---|---|
| Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) | Project/Global |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) | Global |
| Claude Code | .mcp.json (project) or ~/.claude/mcp.json (global) | Project/Global |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | Global |
Detect which client is in use from the environment or conversation context. If unclear, ask.
| Client | How to reload |
|---|---|
| Cursor | Cmd+Shift+P → "Reload Window" |
| Claude Desktop | Quit and reopen the app |
| Claude Code | Run /mcp to check status, restart if needed |
| Windsurf | Cmd+Shift+P → "Reload Window" |
Casual and efficient. Don't explain MCP or protocol details. Just get them to the right place fast. If something breaks, be direct: "That didn't work. Let's try..."