Installation guide
How to install Zapier MCP
In Claude Desktop, ChatGPT, Cursor and Claude Code, with what to check before you start and the first prompts to run.
Zapier MCP is a remote server hosted by Zapier. You create a server in your Zapier account, choose which apps and actions it can use, then add the server address to your AI tool and authorize it. Nothing is installed on your computer. Zapier keeps your app credentials in its own connection layer rather than passing them to the model.
Have someone who already manages your Zapier account and its connected apps do this, such as an operations lead or the Zapier account owner. Use a Zapier account your business controls, not a personal one that could leave the company. Because the server can write to connected apps, start with a short list of actions and expand only after supervised tests.
Before you start
- A Zapier account. The vendor says MCP is included in every Zapier plan, but check your workspace has not had MCP disabled by an admin.
- The apps you want to use (for example Google Sheets, Slack or Gmail) already connected in that Zapier account.
- A short written list of the specific actions the assistant may run, such as 'add row to this sheet', rather than broad access to an app.
- An AI client that supports remote MCP servers: Claude, ChatGPT, Cursor or Claude Code.
- Awareness that each tool call uses two tasks from your existing Zapier task quota, according to the vendor.
- How it runs
- Remote, added by URL
- Access
- Read and write
- Server address
- Copy it from the vendor documentation
Zapier MCP in Claude Desktop
- In Zapier, open Zapier MCP and create a server for your account. Add only the specific actions you want Claude to use.
- Copy the server address that Zapier shows for that server. Take the exact value from Zapier, not from this guide.
- In Claude Desktop, open the connectors or integrations settings and choose the option to add a custom or remote MCP server.
- Paste the server address, give the connection a clear name, and save.
- Follow the sign-in prompt to authorize access to your Zapier account.
- Start a new chat and confirm the Zapier tools are available before running anything. The Zapier page names Claude as a supported client but gives no Claude Desktop menu steps.
Zapier MCP in ChatGPT
- In Zapier, open Zapier MCP and create a server for your account. Add only the specific actions you want ChatGPT to use.
- Copy the server address from Zapier. Use the exact value shown there.
- In ChatGPT, open the settings area for connectors or apps. Availability of custom MCP connectors depends on your ChatGPT plan and workspace settings, which the Zapier page does not cover.
- Add a new connector using a remote MCP server URL, and paste the Zapier server address.
- Authorize the connection when prompted, signing in to the Zapier account that owns the server.
- Start a new chat, enable the connector if ChatGPT asks, and run a read-only test first.
Zapier MCP in Cursor
- In Zapier, open Zapier MCP and create a server for your account. Add only the actions you want Cursor to use.
- Copy the server address from Zapier. Take the exact value from the Zapier page.
- In Cursor, open the settings area for MCP servers and choose to add a new server.
- Add it as a remote server by URL and paste the Zapier server address. The Zapier page names Cursor as supported but does not give the exact config format, so follow Cursor's own MCP documentation for that.
- Authorize the connection with your Zapier account when prompted.
- Confirm the Zapier server shows as connected in Cursor's MCP settings, then try a read-only prompt.
Zapier MCP in Claude Code
- In Zapier, open Zapier MCP and create a server for your account. Add only the specific actions you want Claude Code to use.
- Copy the server address from Zapier. Use the exact value shown there.
- The Zapier page does not mention Claude Code, so use Claude Code's standard way of adding a remote MCP server by URL, and check its documentation for the exact command and options.
- Register the Zapier server address under a clear name, then start a Claude Code session.
- Complete the authorization flow with your Zapier account when Claude Code prompts for it.
- List the available MCP tools in the session to confirm Zapier is connected, then run a read-only test.
Check that it works
Start with questions that only read data. If these answer from your real account, the connection is good.
- List the Zapier tools and apps you can currently use, and tell me which actions you are allowed to run. Do not run any of them.
- Using Zapier, look up the most recent row in the spreadsheet I have connected and summarize it. Do not change anything.
- Search my connected Zapier apps for an action that could send a message to a test channel, and describe what it would do and which fields it needs. Do not run it.
Troubleshooting
+Why does my assistant show no Zapier tools, or can't find the app I want?
Zapier only offers the apps and actions you have enabled, and the app must be connected to your Zapier account. Open the server in Zapier, check the app connection and the allowed actions, then refresh or restart the connection in your AI client. Also ask an admin whether MCP or that app is restricted in your workspace.
+What should I do if sign-in loops or authorization fails?
Sign in to the correct Zapier account in the same browser before authorizing from your AI client, and allow any pop-ups the flow needs. If it keeps looping, remove the server entry in the client, add it again with the server address copied from Zapier, and authorize once more. Managed workspaces may apply IT restrictions.
+An action did something unexpected or used more tasks than I planned. What now?
Open the MCP action History in Zapier to see exactly what ran. The vendor says each tool call uses two tasks from your existing quota, so retries add up. Remove the action from the server's allowed list if it is too broad, tighten your prompt, and test again with a low-stakes action while watching the connected app.
Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.