Zapier status
Three modes for monitoring and maintaining a Zapier MCP setup. Determine the mode from context, or ask if unclear.
For how the Zapier MCP server itself works, see docs.zapier.com/mcp.
Mode 1: Health check
Trigger: "check my tools", "zapier status", "is everything working?", or any general status inquiry.
A quick dashboard view of the current state.
Steps
Inspect the available Zapier MCP tools. The exact surface depends on the server's configuration — some servers expose meta-tools that report the action inventory, others expose each configured action as its own named tool. Use whichever signal is available.
If no Zapier tools are available: report the connection status and suggest running zapier-onboard.
If tools are available, build a summary by grouping them by app:
For each app, show:
- App name
- Number of actions
- Action types (infer read vs write from names: find/search/get/list = read, send/create/update/add = write)
- Quick status: working / needs auth / error
Format as a dashboard:
Zapier MCP status
=================
Server: connected
Total actions: 14 across 5 apps
Slack 3 actions (2 read, 1 write) ✓ working
Gmail 3 actions (1 read, 2 write) ✓ working
Google Cal 2 actions (1 read, 1 write) ✓ working
Jira 3 actions (2 read, 1 write) ✓ working
Google Docs 2 actions (1 read, 1 write) ✓ working
If any actions appear broken (based on recent errors or auth issues), flag them.
End with: "Everything looks good." or "Found [N] issues. Want me to diagnose them?"
Mode 2: Audit
Trigger: "audit my setup", "clean up my tools", "find duplicates", "what should I remove?"
Find inefficiencies: duplicate actions, unused tools, conflicts with native MCP servers.
Steps
Get the full inventory by inspecting the available Zapier MCP tools.
Check for duplicates within Zapier MCP:
- Multiple actions for the same app that do similar things (e.g., both a "find message" and a "search messages" Slack action)
- Recommend removing the less useful one
Check for conflicts with native MCP servers:
- Look at other MCP servers configured in the client's MCP config file (e.g.,
.cursor/mcp.json, claude_desktop_config.json, .mcp.json — depends on the client)
- If the user has both a native Slack MCP and Zapier Slack actions, flag it
- Recommend: "You have Slack through both Zapier and a native Slack server. The native server is usually better for single-app use. Consider removing Zapier's Slack actions."
Check for unused or low-value actions:
- Actions that are rarely useful as defaults (e.g., very specific write actions that are only needed occasionally)
- Suggest removing actions that can be re-added on demand
Show the audit report:
Audit results
=============
Duplicates: 1 found
- Slack: "find_message" and "search_messages" overlap. Recommend removing "search_messages".
Native conflicts: 1 found
- Slack: native Slack MCP also configured. Consider removing Zapier Slack actions.
Cleanup candidates: 2 found
- Google Sheets "delete_row": rarely needed, can re-add on demand
- Jira "add_attachment": niche action, add when needed
Recommended removals: 4 actions
Want me to show you how to clean these up?
- If the user says yes, direct them to mcp.zapier.com to remove the recommended actions (or use the server's in-chat disable tool if available). List exactly which ones to remove.
Mode 3: Diagnose
Trigger: "what's broken?", "my tools aren't working", "debug my MCP", or when a specific tool call has failed.
Systematic troubleshooting with error pattern matching.
Steps
Gather context: Ask what went wrong, or use the error from the current conversation.
Run diagnostics in order:
a. Connection check: Try calling any available Zapier tool. If nothing works, the problem is server-level (auth, config, network).
b. Action check: Is the specific action available on this server? If not, the user needs to add it at mcp.zapier.com (or via the server's in-chat discovery tools if available).
c. Auth check: Try calling a read action for the affected app. If it returns an auth error, the app connection needs re-authentication.
d. Parameter check: Review the failing call's parameters. Common issues:
- Missing required fields
- Wrong field format (IDs vs names)
- Instructions that are too vague for the params resolver
Match against known error patterns:
| Symptom |
Likely cause |
Fix |
| All tools fail |
Server auth expired |
Re-authenticate at mcp.zapier.com |
| One app fails, others work |
App-level auth expired |
Re-connect that specific app |
| Tool not found / unavailable |
Action not configured |
Direct user to mcp.zapier.com to add it |
| "invalid params" |
Wrong fields or format |
Check the tool's parameter schema |
| Results are empty but expected data exists |
Search too narrow or wrong field |
Broaden the search or check field names |
| Timeout on execute |
Server overloaded or action is slow |
Retry once, then report if persistent |
| "rate limit exceeded" |
Too many calls |
Space out requests, wait 30 seconds |
| Works in one project, fails in another |
Project-level vs global config |
Check both project-level and global MCP config for the client |
- Report findings:
"Here's what I found:
- Connection: OK (server responding)
- Actions: 14 tools available across 5 apps
- Auth issue: Gmail connection expired. You need to re-authenticate Gmail at mcp.zapier.com.
- Recommendation: [direct link or specific instruction]"
- If the fix requires user action (re-auth, config change), provide the specific link or instruction. If it's something the AI can fix (adjust parameters, try a different tool), offer to do it.
General notes
- Always inspect the available Zapier MCP tools as the first diagnostic step in any mode.
- Don't dump raw error messages. Translate them into plain language.
- If a problem is beyond what the skill can diagnose (server-side bug, API outage), say so and suggest checking status.zapier.com or contacting support.
1---2name: zapier-status3description: Check the health of your Zapier MCP setup. Three modes — health check (dashboard view), audit (find waste and duplicates), diagnose (systematic troubleshooting). Use when asking "is my MCP working?", "check my tools", "audit my setup", "what's broken?", or "zapier status".4metadata:5 source: https://skillmd.com/skills/zapier/zapier-status6---78# Zapier status910Three modes for monitoring and maintaining a Zapier MCP setup. Determine the mode from context, or ask if unclear.1112For how the Zapier MCP server itself works, see [docs.zapier.com/mcp](https://docs.zapier.com/mcp/home).1314## Mode 1: Health check1516**Trigger:** "check my tools", "zapier status", "is everything working?", or any general status inquiry.1718A quick dashboard view of the current state.1920### Steps21221. Inspect the available Zapier MCP tools. The exact surface depends on the server's configuration — some servers expose meta-tools that report the action inventory, others expose each configured action as its own named tool. Use whichever signal is available.23242. If no Zapier tools are available: report the connection status and suggest running **zapier-onboard**.25263. If tools are available, build a summary by grouping them by app:2728**For each app**, show:2930- App name31- Number of actions32- Action types (infer read vs write from names: find/search/get/list = read, send/create/update/add = write)33- Quick status: working / needs auth / error3435**Format as a dashboard:**3637```38Zapier MCP status39=================40Server: connected41Total actions: 14 across 5 apps4243Slack 3 actions (2 read, 1 write) ✓ working44Gmail 3 actions (1 read, 2 write) ✓ working45Google Cal 2 actions (1 read, 1 write) ✓ working46Jira 3 actions (2 read, 1 write) ✓ working47Google Docs 2 actions (1 read, 1 write) ✓ working48```49504. If any actions appear broken (based on recent errors or auth issues), flag them.51525. End with: "Everything looks good." or "Found [N] issues. Want me to diagnose them?"5354## Mode 2: Audit5556**Trigger:** "audit my setup", "clean up my tools", "find duplicates", "what should I remove?"5758Find inefficiencies: duplicate actions, unused tools, conflicts with native MCP servers.5960### Steps61621. Get the full inventory by inspecting the available Zapier MCP tools.63642. **Check for duplicates within Zapier MCP:**65 - Multiple actions for the same app that do similar things (e.g., both a "find message" and a "search messages" Slack action)66 - Recommend removing the less useful one67683. **Check for conflicts with native MCP servers:**69 - Look at other MCP servers configured in the client's MCP config file (e.g., `.cursor/mcp.json`, `claude_desktop_config.json`, `.mcp.json` — depends on the client)70 - If the user has both a native Slack MCP and Zapier Slack actions, flag it71 - Recommend: "You have Slack through both Zapier and a native Slack server. The native server is usually better for single-app use. Consider removing Zapier's Slack actions."72734. **Check for unused or low-value actions:**74 - Actions that are rarely useful as defaults (e.g., very specific write actions that are only needed occasionally)75 - Suggest removing actions that can be re-added on demand76775. **Show the audit report:**7879```80Audit results81=============82Duplicates: 1 found83 - Slack: "find_message" and "search_messages" overlap. Recommend removing "search_messages".8485Native conflicts: 1 found86 - Slack: native Slack MCP also configured. Consider removing Zapier Slack actions.8788Cleanup candidates: 2 found89 - Google Sheets "delete_row": rarely needed, can re-add on demand90 - Jira "add_attachment": niche action, add when needed9192Recommended removals: 4 actions93Want me to show you how to clean these up?94```95966. If the user says yes, direct them to [mcp.zapier.com](https://mcp.zapier.com) to remove the recommended actions (or use the server's in-chat disable tool if available). List exactly which ones to remove.9798## Mode 3: Diagnose99100**Trigger:** "what's broken?", "my tools aren't working", "debug my MCP", or when a specific tool call has failed.101102Systematic troubleshooting with error pattern matching.103104### Steps1051061. **Gather context:** Ask what went wrong, or use the error from the current conversation.1071082. **Run diagnostics in order:**109110 a. **Connection check:** Try calling any available Zapier tool. If nothing works, the problem is server-level (auth, config, network).111112 b. **Action check:** Is the specific action available on this server? If not, the user needs to add it at mcp.zapier.com (or via the server's in-chat discovery tools if available).113114 c. **Auth check:** Try calling a read action for the affected app. If it returns an auth error, the app connection needs re-authentication.115116 d. **Parameter check:** Review the failing call's parameters. Common issues:117 - Missing required fields118 - Wrong field format (IDs vs names)119 - Instructions that are too vague for the params resolver1201213. **Match against known error patterns:**122123| Symptom | Likely cause | Fix |124| ------------------------------------------ | ----------------------------------- | ------------------------------------------------------------- |125| All tools fail | Server auth expired | Re-authenticate at mcp.zapier.com |126| One app fails, others work | App-level auth expired | Re-connect that specific app |127| Tool not found / unavailable | Action not configured | Direct user to mcp.zapier.com to add it |128| "invalid params" | Wrong fields or format | Check the tool's parameter schema |129| Results are empty but expected data exists | Search too narrow or wrong field | Broaden the search or check field names |130| Timeout on execute | Server overloaded or action is slow | Retry once, then report if persistent |131| "rate limit exceeded" | Too many calls | Space out requests, wait 30 seconds |132| Works in one project, fails in another | Project-level vs global config | Check both project-level and global MCP config for the client |1331344. **Report findings:**135136"Here's what I found:137138- **Connection**: OK (server responding)139- **Actions**: 14 tools available across 5 apps140- **Auth issue**: Gmail connection expired. You need to re-authenticate Gmail at mcp.zapier.com.141- **Recommendation**: [direct link or specific instruction]"1421435. If the fix requires user action (re-auth, config change), provide the specific link or instruction. If it's something the AI can fix (adjust parameters, try a different tool), offer to do it.144145## General notes146147- Always inspect the available Zapier MCP tools as the first diagnostic step in any mode.148- Don't dump raw error messages. Translate them into plain language.149- If a problem is beyond what the skill can diagnose (server-side bug, API outage), say so and suggest checking [status.zapier.com](https://status.zapier.com) or contacting support.