MCP Urgent Caller Triage
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.
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.
Install Zapier Onboard
$ npx skills add zapier/zapier-mcp --skill zapier-onboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/zapier-mcp zapier-onboard --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-onboard .claude/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .claude/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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-onboardType 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-onboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/zapier-mcp zapier-onboard --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-onboard .agents/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .agents/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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-onboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/zapier-mcp zapier-onboard --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-onboard .cursor/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .cursor/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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-onboard--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-onboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/zapier-mcp zapier-onboard --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-onboard .gemini/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .gemini/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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-onboardInstalls 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-onboard -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-onboard .github/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .github/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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-onboard -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-onboard --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-onboard .opencode/skills/zapier-onboard && 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-onboard" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-onboard into .opencode/skills/zapier-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-onboard", 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.
Facts
- Skill name
zapier-onboard- GitHub stars
- 430
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,338 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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 in 2 steps: Introduction → Diagnose
- Getting started
- SKILL.md covers Step 1: Introduction, Step 2: Diagnose, Branch: Healthy and Branch: Auth broken, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Zapier Onboard is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. 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. Use when getting started, troubleshooting connection issues, or when the user asks "what is Zapier MCP", "how do I get started with Zapier", "set me up", "what can I do with Zapier", or "tell me about Zapier".
Its SKILL.md is about 2.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. It works with Zapier and Model Context Protocol. 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.
When your agent uses it
- Getting started
- Troubleshooting connection issues
- The user asks what is Zapier MCP
- How do I get started with Zapier
Example prompts
- “what is Zapier MCP”
- “how do I get started with Zapier”
- “set me up”
- “/zapier-onboard”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5360f15. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
Links to these hosts (documentation or services it may open):
mcp.zapier.comdocs.zapier.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Zapier Onboard loads about 2.8k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 1,338 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from zapier/zapier-mcp at commit 5360f15, republished under its MIT licence (© zapier). 1,338 words, ~2,838 tokens.
Download SKILL.mdSave it as
.claude/skills/zapier-onboard/SKILL.md (or your agent's skills folder).- name
- zapier-onboard
- description
- 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. Use when getting started, troubleshooting connection issues, or when the user asks "what is Zapier MCP", "how do I get started with Zapier", "set me up", "what can I do with Zapier", or "tell me about Zapier".
Zapier onboard
Introduce Zapier MCP, get the user authenticated, then guide them through the appropriate setup flow.
For how the Zapier MCP server itself works, see docs.zapier.com/mcp.
Step 1: Introduction
Start by describing what Zapier MCP can do for the user, then get them authenticated.
Pitch
"Zapier MCP connects your AI assistant to 9,000+ apps — Slack, Gmail, Google Calendar, Jira, Notion, HubSpot, and thousands more. Once set up, you can search across your tools, take actions, and automate workflows, all through natural conversation. It's personalized to your workflow — you pick the apps and actions that matter to you, and your AI learns to use them."
Check connection
Check if any Zapier MCP tools are available:
Tools are available: The user is already authenticated. Give a shorter version of the pitch — "You've got Zapier MCP installed and connected. Let me check what you have set up." — then proceed to Step 2.
No Zapier tools available at all: The server is installed but needs authentication. First, attempt to authenticate directly in the chat by calling
mcp_authon the Zapier MCP server. If that succeeds, re-check available tools and proceed to Step 2.If
mcp_authfails or is unavailable, fall back to manual instructions based on their client:- In Cursor: "Let's get you connected. Go to Settings > Cursor Settings > Tools & MCP and click Connect next to the Zapier MCP server. You can also press Cmd+Shift+P and search for 'MCP' to get there quickly."
- In Claude Desktop: "Let's get you connected. Go to Customize > Connectors > Zapier and click Connect."
- In other clients: "Let's get you connected. Find the Zapier MCP server in your client's MCP settings and click Connect. This will redirect you to mcp.zapier.com to sign in."
Detect which client is in use from the environment or conversation context. If unclear, give the generic instructions.
Wait for the user to confirm ("done"), then re-check available tools and proceed to Step 2.
Step 2: Diagnose
Inspect the available Zapier MCP tools. The result determines which branch to follow:
| Result | Branch |
|---|---|
| Zapier action tools are available (beyond the configuration tools) | Healthy |
| Only configuration tools available (no actions yet) | Fresh install |
| Calls fail with auth/401 errors | Auth broken |
| No Zapier tools available at all | Not connected |
Branch: Healthy
The server is connected and has actions configured. Show a summary and offer next steps.
- Look at the available Zapier MCP tools and group them by app.
- Show a clean summary:
"Your Zapier MCP is connected with [N] tools across [app list]:
- Slack: ...
- Gmail: ...
- Google Calendar: ...
Everything's working. What would you like to do?"
- Offer options:
- "Try one live" → trigger the zapier-demo skill for a first-action walkthrough
- "Add more tools" → trigger the zapier-explore skill to build out a role-tailored toolkit
- "Run a health check" → trigger the zapier-status skill
- Or just start using the tools
Branch: Auth broken
The server exists in the config but authentication has expired or is invalid.
- Tell the user:
"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."
- Wait for the user to confirm.
- Try calling a Zapier tool again to verify.
- If it works: show the Healthy summary.
- If it still fails: suggest deleting and recreating the server config. Offer to help update the MCP config file with a fresh token (see "MCP config by client" below).
Branch: Not connected
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.
Attempt to authenticate directly in the chat by calling
mcp_authon the Zapier MCP server. If that succeeds, skip to step 5.If
mcp_authfails or is unavailable, fall back to manual instructions based on their client:- In Cursor: "Go to Settings > Cursor Settings > Tools & MCP and click Connect next to the Zapier MCP server. You can also press Cmd+Shift+P and search for 'MCP' to get there quickly."
- In Claude Desktop: "Go to Customize > Connectors > Zapier and click Connect."
- In other clients: "Find the Zapier MCP server in your client's MCP settings and connect it. This will redirect you to mcp.zapier.com to sign in."
Detect which client is in use from the environment or conversation context. If unclear, give the generic instructions.
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 actions yet).
Branch: Fresh install
The server is connected but has no actions configured. The user needs to add actions through Zapier.
Show full SKILL.md (536 more words)Show less
Step 1: Workflow-first discovery
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."
Direct the user to mcp.zapier.com (or call the server's configuration-URL tool if available) so they 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."
Step 2: Guide configuration
Recommend specific actions the user should add for each app. 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.
"Add those actions and connect your app accounts in the Zapier dashboard. Come back and say done when you're finished."
Step 3: Verify
After the user confirms, check the available Zapier MCP tools to see what was added. If new tools appeared, show a summary. If nothing changed, the user may need to reload their client (see "Reload instructions by client" below).
Step 4: Wrap up
Once everything is connected:
- Show a final summary of the setup.
- Hand off to the natural next step:
"You're set up. Want to try one live? Run /zapier-demo to see one action work, or /zapier-explore if you want to keep building out the toolkit."
MCP config by client
| 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.
Reload instructions by client
| 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" |
Tone
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..."
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/zapier/skills/zapier-onboard of zapier/zapier-mcp.
Open the folder on GitHubat commit 5360f15
Compare with similar skills
Zapier Onboard 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 Onboard this skillzapier/zapier-mcp | 430 | — | ~2.8k | Automated safety check: Pass | MIT | |
| MCP Urgent Caller Triagezapier/gtm-cheat-codes | 342 | — | ~1k | Automated safety check: Pass | MIT | |
| Zapierasgeirtj/system_prompts_leaks | 69k | — | ~328 | Automated safety check: Pass | CC0-1.0 | |
| N8nericrisco/rsc-harness | 180 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Zapierericrisco/rsc-harness | 180 | — | ~2.8k | Automated safety check: Notes | MIT | |
| Zapier Workflowsdavila7/claude-code-templates | 33k | 2 repos | ~4.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Zapier
asgeirtj/system_prompts_leaks
Connect Muse to actions across apps through Zapier's official MCP server.
N8n
ericrisco/rsc-harness
A skill your agent uses when operating a live n8n instance programmatically — its REST API ({host}/api/v1, X-N8N-API-KEY) or the n8n-mcp server — to create, validate, test, activate, update, delete…
Zapier
ericrisco/rsc-harness
A skill your agent uses when operating Zapier from an agent through the official hosted Zapier MCP server — connecting with a bearer key, discovering an app's actions, enabling one, and invoking a…
Zapier Workflows
davila7/claude-code-templates
Manage and trigger pre-built Zapier workflows and MCP tool orchestration.
- Official
Apify Integration Development
apify/agent-skills
Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.
More from zapier/zapier-mcp
- Official
Zapier Demo
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
- Official
Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
- Official
Zapier Explore
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…
Related
Works with
Categories
Questions about Zapier Onboard
What does Zapier Onboard do?
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. Zapier Onboard is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. 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.
When should I use Zapier Onboard?
Zapier Onboard fits situations like: getting started; troubleshooting connection issues; the user asks what is Zapier MCP; how do I get started with Zapier.
How do I install Zapier Onboard in Claude Code?
Run `npx skills add zapier/zapier-mcp --skill zapier-onboard -a claude-code`. Or copy the skill folder (plugins/zapier/skills/zapier-onboard in zapier/zapier-mcp) into .claude/skills/zapier-onboard in your project. Claude Code loads it when a task matches its description.
How do I install Zapier Onboard in Codex?
Run `npx skills add zapier/zapier-mcp --skill zapier-onboard -a codex`. Or copy the skill folder (plugins/zapier/skills/zapier-onboard in zapier/zapier-mcp) into .agents/skills/zapier-onboard in your project. Codex loads it when a task matches its description.
Can I use Zapier Onboard in Cursor, Gemini CLI or GitHub Copilot?
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-onboard -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-onboard, .gemini/skills/zapier-onboard, .github/skills/zapier-onboard and .opencode/skills/zapier-onboard in your project.
What does Zapier Onboard need to run?
SKILL.md names no scripts, command-line tools or credentials: Zapier Onboard is instructions for the agent only.
Does Zapier Onboard access the network?
SKILL.md names 2 domains. As links in the text: mcp.zapier.com and docs.zapier.com. This is read from the text; nothing was executed.
Is Zapier Onboard safe to install?
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.
What licence does Zapier Onboard use?
Zapier Onboard is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Zapier Onboard use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Zapier Onboard?
Skills that share tags, products or a category with Zapier Onboard: MCP Urgent Caller Triage (zapier/gtm-cheat-codes, 342 stars), Zapier (asgeirtj/system_prompts_leaks, 69k stars), N8n (ericrisco/rsc-harness, 180 stars) and Zapier (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Zapier Onboard?
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.