Let your agent connect to anything
Authenticated, governed access to the full Zapier catalog β in code, on behalf of your users. No OAuth flows. No token management. Zapier handles the keys.
MCP and SDK
When to use MCP vs. SDK
Use SDK when you're working with code or building Zapier capabilities into your app/product. Use MCP to expose Zapier connections to AI apps and agents that can't execute code.
Zapier MCP, Zapier SDK, and Zapier CLI: What's the difference?
Zapier gives you three ways to let AI access your apps. Zapier MCP runs in chatbots like Claude and ChatGPT. Zapier SDK runs in code files. Zapier CLI runs in your terminal.
Zapier SDK: Connect your code files to thousands of actions
A guide to the Zapier SDK. Plug your AI coding agent into 9,000+ apps β with auth, governance, and reliability built in.
Zapier MCP: Perform tens of thousands of actions in your AI tool
Same app ecosystem, different surface. Zapier MCP plugs Claude, ChatGPT, and other AI chatbots into 9,000+ apps β no code required.
Built for builders and their agents
Already using Zapier? The SDK is your next step β take your connected apps and put them to work in code.
Vibe coders & AI builders: Set up in an afternoon. Ship by end of day.
Already building in Cursor or Claude Code? Install SDK in 5 minutes. Your agent calls the same interface you do β Zapier handles auth, retries, and governance so neither of you has to.
Developers: Skip the Auth. Just build.
9,000+ prebuilt apps plus raw API access. One interface, no OAuth setup required. Your product calls it, your agent calls it β either way Zapier handles the integration layer.
Prosumers & non-devs: Your agent connects to your apps.
Being carried along by the agent wave. The SDK is what makes your agent actually do real work β connecting to the apps you already use.
How it works
Install and initialize
One npm install. Run zapier-sdk login. That's it β you're authenticated. Whether you're writing the code or your agent is, the SDK gives you a programmable interface to the entire Zapier ecosystem from that point forward.
Connect your apps once
Your existing Zapier connections are ready to go. If you need to add a new one, the SDK generates a connect link β your user authenticates through a Zapier-hosted flow and lands back in your context. Tokens, refresh logic, and retries never touch your code.
Your agent takes action
Invoke any of 9,000+ apps across the full catalog, or use raw authenticated API calls to 3,000+ supported apps. Zapier's governance policies apply automatically β no extra config.
Everything we handle. Nothing you maintain.
Build through the surfaces you and your agent already use, while Zapier still handles the hard parts underneath.
β 9,000+ apps
β App + Action governance
β Auth managed for every app
β Raw API for 3,000+ apps
β 15yrs of API knowledge
β Rate limit handling
Free. Seriously.
The SDK is free during open beta. Here's what's included:
β‘ Access to 9,000+ apps
π€ Raw API access for 3,000+ apps
π¬ 30,000+ actions
You will be notified before any billing changes occur.
FAQs
What is Zapier SDK?
Zapier SDK gives coding agents and builders authenticated access to 9,000+ apps through one interface. Run pre-built actions, make raw API calls to 3,000+ app endpoints, and chain complex logic across services. Zapier handles all the auth, token refresh, and retries. Your code handles the logic.
Who is the SDK for?
Anyone building in code or using a coding agent (Cursor, Claude Code, VS Code, Codex). The SDK is the interface for when your agent needs to connect to real apps, take actions, and handle edge cases programmatically. It works whether you're shipping a weekend project or embedding Zapier into a production product.
Can my AI agent use the SDK directly?
Yes. The SDK is built for agents that write and execute code. Your agent installs the SDK, authenticates, and starts calling APIs across 9,000+ apps on its own. It handles loops, conditionals, error recovery, and multi-step workflows that go beyond what a single pre-built action can do.
How is this different from Zapier MCP?
Same apps, same capabilities, different interface. MCP works through chat (Claude, ChatGPT) and gives agents a curated menu of actions. SDK works through code (editors, scripts, production apps) and gives agents full programmatic control, including raw API access. Most builders use more than one β SDK, MCP, and CLI (npx zapier) each fit a different environment.
Do I need to manage OAuth or API keys?
No. Zapier manages authentication for every app. Credentials are never exposed to the AI model or your code. Your user authenticates once through a Zapier-hosted flow, and the SDK handles tokens, refresh, scopes, and retries from that point forward.
Why not just build integrations myself?
You could. But you'd be solving OAuth for each app, handling token refresh and rotation, managing webhook subscriptions, dealing with rate limits and API quirks, and maintaining all of it as vendors change their APIs. Zapier has maintained these integrations across 9,000+ apps for 15 years. The SDK gives you one interface to all of it, so you can focus on your product instead of plumbing.
What can I do beyond pre-built actions?
The SDK includes raw authenticated API access to 3,000+ app endpoints. If a pre-built action doesn't cover your use case, you can call any supported API endpoint directly through Zapier's infrastructure with full auth handled. Write custom queries, hit undocumented endpoints, build workflows that no pre-built action anticipated.
How much does the SDK cost?
Free during open beta. Full access to 9,000+ apps, 30,000+ actions, and raw API calls at no cost. You'll be notified before any billing changes happen.
Is the SDK secure?
Zapier manages all third-party credentials. API keys never touch the model or your codebase. If your org has restricted specific apps or actions inside Zapier, those policies apply automatically to SDK traffic. The same credential infrastructure that's run Zapier for 15 years handles every connection.
Isn't Zapier just a no-code automation tool?
Zapier runs the largest app integration network in the world: 9,000+ apps, 30,000+ actions, maintained continuously since 2012. The SDK is how coding agents and builders access that same network programmatically. No drag-and-drop, no UI. Pure code, typed interfaces, and full API access.
Your agent. Every app. Zapier handles the rest.
One interface for your code and your agents. Zapier handles the keys β you handle the logic.