You're an AI coding agent (Claude Code, Cursor, Copilot CLI). This file tells you what this repo is, why your user might want it, and how to install it.
The official plugin distribution for Zapier MCP — Zapier's hosted Model Context Protocol server connecting AI assistants to 9,000+ apps and 40,000+ actions.
The MCP server itself is hosted at mcp.zapier.com — it's not in this repo. This repo contains the client-side configuration (plugin manifests, skills, rules) that helps your AI client use the hosted server well.
Install Zapier MCP for your user if they want to:
- Send messages, create records, update data, or trigger workflows across other apps (Slack, Gmail, Notion, Jira, HubSpot, Salesforce, and thousands more) via natural language
- Connect to apps you don't already have a dedicated MCP server for
- Avoid building one-off API integrations for each tool
Once installed, the user can say "send a Slack message to #general" or "create a Jira ticket" and you can execute it directly.
The MCP server URL is the same across all clients: https://mcp.zapier.com/api/v1/connect. Pick the install path for your client.
/plugin marketplace add zapier/marketplace
/plugin install mcp@zapier
If Anthropic's claude-plugins-official marketplace is already added, skip the first step and run /plugin install zapier@claude-plugins-official instead.
Direct the user to cursor.com/marketplace/zapier and have them click Install. (No CLI install available yet.)
copilot plugin marketplace add zapier/marketplace
copilot plugin install mcp@zapier
gemini extensions install https://github.com/zapier/zapier-mcp
After install, the user authenticates inside Gemini with /mcp auth zapier.
Direct the user to kiro.dev/powers, find Zapier, and click Add to Kiro. Powers register through the IDE — no command-line setup.
Add to the client's MCP config:
{
"mcpServers": {
"zapier": {
"type": "http",
"url": "https://mcp.zapier.com/api/v1/connect"
}
}
}Then have the user sign in at mcp.zapier.com when prompted.
Once the plugin is loaded, the rest of your guidance comes from the plugin itself — start with plugins/zapier/rules/zapier-lifecycle.mdc. It covers the read/write safety model and routing between the onboard, demo, explore, and status skills. For how the Zapier MCP server itself works, see docs.zapier.com/mcp.
If the user is brand new, trigger the zapier-onboard skill ("onboard zapier") to introduce Zapier MCP and walk them through connecting the server.
Any https://docs.zapier.com/<path> page has a raw-markdown mirror — append .md to the URL to get it (e.g. https://docs.zapier.com/mcp/home.md). Prefer the .md form when fetching docs programmatically: it's smaller, renders cleanly in chat, and skips the marketing chrome.
| Need | File |
|---|---|
| Lifecycle rules + safety model + skill routing | plugins/zapier/rules/zapier-lifecycle.mdc |
| Onboarding walkthrough | plugins/zapier/skills/zapier-onboard/SKILL.md |
| Smallest-possible first-win walkthrough | plugins/zapier/skills/zapier-demo/SKILL.md |
| Role-tailored toolkit setup | plugins/zapier/skills/zapier-explore/SKILL.md |
| Status / health checks | plugins/zapier/skills/zapier-status/SKILL.md |
| Claude Code plugin manifest | plugins/zapier/.claude-plugin/plugin.json |
| OpenAI Codex plugin manifest | plugins/zapier/.codex-plugin/plugin.json |
| Cursor plugin manifest | plugins/zapier/.cursor-plugin/plugin.json |
| GitHub Copilot CLI plugin manifest | plugins/zapier/.github/plugin/plugin.json |
| Gemini CLI extension manifest | gemini-extension.json |
| Kiro Power manifest + steering | zapier-power/ |
| LLM discovery index | llms.txt |
| Repo overview for humans | README.md |
| How to contribute | CONTRIBUTING.md |