ClaudeSuperPower

zapier-status

Skill

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".

Install

git clone https://github.com/zapier/zapier-mcp.git ~/.claude/skills/zapier-status

What is zapier-status?

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".

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~68 tokens of context used while enabled, before you invoke anything

Documentation

README · ~5 min read

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

  1. 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.

  2. If no Zapier tools are available: report the connection status and suggest running zapier-onboard.

  3. If tools are available, build a summary by grouping them by app:

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills