Creativity · MCP — server
MCP Zapier Server
The MCP Zapier Server bridges the Model Context Protocol with Zapier's action catalog. Because Zapier already has pre-built integrations for thousands of SaaS apps, a single MCP server gives an LLM client access to Gmail, HubSpot, Trello, Notion, Airtable and more — behind one OAuth flow and one set of rate limits.
MCP facts
- Kind
- server
- Ecosystem
- anthropic-mcp
- Language
- TypeScript / Node.js
- Transports
- stdio, http
Capabilities
- Tools: list_available_actions, run_action, search_app
- Per-user OAuth via Zapier's consent flow
- Dynamic tool registration — the catalog changes as the user enables actions
Install
npx -y @modelcontextprotocol/server-zapier Configuration
{
"mcpServers": {
"zapier": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-zapier"],
"env": { "ZAPIER_NLA_API_KEY": "sk-ak-..." }
}
}
} Frequently asked questions
Does Zapier publish this server officially?
Zapier has released official MCP and AI Actions endpoints. Several wrappers around them are also community-maintained; both approaches are valid.
How does user consent work?
Zapier handles OAuth for each downstream app. The model never sees those credentials — it just invokes the Zapier action the user has pre-enabled.
Is there a free tier?
Yes, Zapier offers a limited free tier for AI Actions; production usage usually needs a paid plan.
Sources
- Zapier AI Actions — accessed 2026-04-20
- MCP servers index — accessed 2026-04-20