What is Zapier MCP?
Zapier MCP is the Model Context Protocol interface to Zapier. It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records, under the same governance model that applies to the rest of Zapier: workspace-level access controls, user permissions, and audit history. Zapier is SOC 2 Type II certified. If you do not write code, use your preferred MCP client with Zapier. Describe what you want in a conversation and your AI handles the rest. If you are building an application, MCP gives you thousands of pre-built actions instead of an integration you write for each app. Plugin manifests, onboarding skills, and lifecycle rules are at github.com/zapier/zapier-mcp.How Zapier MCP works
Zapier MCP has three parts:- Your MCP server. It holds the apps, actions, and skills your AI can use. Several MCP clients can connect to the same server, so you can set up Claude and Cursor once.
- Your MCP client. Any application that supports MCP, such as Claude, ChatGPT, Cursor, Grok Bot, or VS Code. Every MCP client connects to the same endpoint, and most sign in with OAuth.
- Tools. Anything your MCP client can call. An action is something an app can do, such as Send Channel Message in Slack. Actions run through the same app connections as your Zaps.
When to use Zapier MCP
- Acting on something you are already discussing. Your AI has the context of the conversation, so it can create the task or send the message without you restating the details.
- Working across several apps in one request. Pull data from one app and write it to another, such as finding a contact in your CRM and then emailing them.
- One-off actions and full automations. Use Zapier MCP for requests you make once, in the moment, or to build workflows that run repeatedly on a trigger. With Next Gen Zaps (early access), you describe what you want and your AI builds and deploys it to Zapier through MCP.
- Giving a coding assistant access to your stack. Assistants such as Cursor and VS Code can create issues, post updates, and check records without you leaving your editor.
Popular integrations
Gmail
Send emails, search messages, manage labels
Google Sheets
Add rows, update data, create spreadsheets, find data
Google Calendar
Find events, create meetings, check availability
Slack
Send messages, create channels, update status
Jira
Create tasks, update epics, search stories
Asana
Create tasks, update projects, add comments
GitHub
Create issues, manage PRs, update repos
HubSpot
Manage contacts, create deals, update records
Example use cases
Personal productivity
- “Add this meeting to my calendar and notify the team in Slack”
- “Create a task in Asana for each unread email from clients”
- “Save this information to my Notion database”
Sales and marketing
- “Find all leads from last week and add them to our CRM”
- “Send a personalized follow-up email to each new subscriber”
- “Update the deal status in HubSpot and notify the sales channel”
Development and operations
- “Create a GitHub issue for this bug report”
- “Post deployment notes to our Discord channel”
- “Update the project status in Linear and notify stakeholders”
Limitations
- Your MCP client must support MCP over Streamable HTTP. Zapier MCP does not support Server-Sent Events (SSE).
- Sharing a server needs a Team or Enterprise plan. On any plan, you can share a copy of your tool list as a tool bundle instead.
- Tool calls use tasks. Each successful call uses two tasks from your Zapier plan, and failed calls do not count. Check Usage and billing for details.
Get started
Quickstart
Pick your MCP client, connect it, and run your first tool call end to end.
How servers work
What a server contains, and how several MCP clients use one server.