MCP Sheet Cache Bridge
zapier/gtm-cheat-codes
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
$ npx skills add zapier/zapier-mcp --skill zapier-status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/zapier-mcp zapier-status --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .claude/skills/zapier-status && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .claude/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-statusType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zapier/zapier-mcp --skill zapier-status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/zapier-mcp zapier-status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .agents/skills/zapier-status && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .agents/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/zapier-mcp --skill zapier-status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/zapier-mcp zapier-status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .cursor/skills/zapier-status && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .cursor/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zapier/zapier-mcp.git --path plugins/zapier/skills/zapier-status--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zapier/zapier-mcp --skill zapier-status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/zapier-mcp zapier-status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .gemini/skills/zapier-status && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .gemini/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zapier/zapier-mcp zapier-statusInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zapier/zapier-mcp --skill zapier-status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .github/skills/zapier-status && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .github/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/zapier-mcp --skill zapier-status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/zapier-mcp zapier-status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/zapier/skills/zapier-status .opencode/skills/zapier-status && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "zapier-status" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-status into .opencode/skills/zapier-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-status", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
zapier-statusCheck the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
Zapier Status is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. 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".
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Workflow automation and MCP servers. It works with Zapier, Model Context Protocol and Slack. The repository describes itself as: Official plugin distribution for the hosted Zapier MCP server. Install it in your AI client and connect to thousands of apps. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 5360f15. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.zapier.commcp.zapier.comstatus.zapier.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Zapier Status loads about 1.8k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 789 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from zapier/zapier-mcp at commit 5360f15, republished under its MIT licence (© zapier). 789 words, ~1,830 tokens.
.claude/skills/zapier-status/SKILL.md (or your agent's skills folder).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.
Trigger: "check my tools", "zapier status", "is everything working?", or any general status inquiry.
A quick dashboard view of the current state.
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:
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) ✓ workingIf 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?"
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.
Get the full inventory by inspecting the available Zapier MCP tools.
Check for duplicates within Zapier MCP:
Check for conflicts with native MCP servers:
.cursor/mcp.json, claude_desktop_config.json, .mcp.json — depends on the client)Check for unused or low-value actions:
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?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.
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:
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 |
"Here's what I found:
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/zapier/skills/zapier-status of zapier/zapier-mcp.
Open the folder on GitHubat commit 5360f15
Zapier Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Zapier Status this skillzapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT | |
| MCP Sheet Cache Bridgezapier/gtm-cheat-codes | 342 | — | ~905 | Automated safety check: Pass | MIT | |
| MCP Urgent Caller Triagezapier/gtm-cheat-codes | 342 | — | ~1k | Automated safety check: Pass | MIT | |
| Zapier Workflowsdavila7/claude-code-templates | 33k | 2 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Install Zapierzapier/gtm-cheat-codes | 342 | — | ~577 | Automated safety check: Pass | MIT | |
| Media Inbox Triagezapier/gtm-cheat-codes | 342 | — | ~1.6k | Automated safety check: Pass | MIT |
zapier/gtm-cheat-codes
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
davila7/claude-code-templates
Manage and trigger pre-built Zapier workflows and MCP tool orchestration.
zapier/gtm-cheat-codes
Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.
zapier/gtm-cheat-codes
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
ericrisco/rsc-harness
A skill your agent uses when operating Make.com (formerly Integromat) programmatically — driving its REST API v2 or the Make MCP server from code or an agent to create, read, update, activate, run…
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
zapier/zapier-mcp
Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions…
zapier/zapier-mcp
Onboard a new user to Zapier MCP — introduce what it can do, walk through authentication, and route into the right flow based on the state of their setup.
Works with
Categories
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp. Zapier Status is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. Check the health of your Zapier MCP setup.
Zapier Status fits situations like: asking is my MCP working?; tasks that involve Workflow automation; tasks that involve MCP servers.
Run `npx skills add zapier/zapier-mcp --skill zapier-status -a claude-code`. Or copy the skill folder (plugins/zapier/skills/zapier-status in zapier/zapier-mcp) into .claude/skills/zapier-status in your project. Claude Code loads it when a task matches its description.
Run `npx skills add zapier/zapier-mcp --skill zapier-status -a codex`. Or copy the skill folder (plugins/zapier/skills/zapier-status in zapier/zapier-mcp) into .agents/skills/zapier-status in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/zapier-mcp --skill zapier-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zapier-status, .gemini/skills/zapier-status, .github/skills/zapier-status and .opencode/skills/zapier-status in your project.
SKILL.md names no scripts, command-line tools or credentials: Zapier Status is instructions for the agent only.
SKILL.md names 3 domains. As links in the text: docs.zapier.com, mcp.zapier.com and status.zapier.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Zapier Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Zapier Status: MCP Sheet Cache Bridge (zapier/gtm-cheat-codes, 342 stars), MCP Urgent Caller Triage (zapier/gtm-cheat-codes, 342 stars), Zapier Workflows (davila7/claude-code-templates, 33k stars) and Install Zapier (zapier/gtm-cheat-codes, 342 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
zapier (a GitHub organization, an official publisher) maintains it in zapier/zapier-mcp, which has 430 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 29, 2026.
Source: zapier/zapier-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.