Zapier MCP Server Status
Is the Zapier MCP server up? Live check of mcp.zapier.com, plus the fixes that solve most connection problems.
The check above sends the official Zapier MCP endpoint https://mcp.zapier.com/api/mcp/mcp the first request every MCP client sends. Up with HTTP 401 is the normal state: the server answers and asks for sign-in. If it is up and your connector still fails, work through the fixes below.
| MCP server URL | https://mcp.zapier.com/api/mcp/mcp |
| Older SSE endpoint | https://mcp.zapier.com/api/mcp/sse |
| Transport | Streamable HTTP |
| Authentication | an API key |
| Product | Zapier |
Zapier MCP not working? Fix it in this order
- Look at the live check above. If it says Down, the problem is on Zapier's side and usually clears up on its own; check again in a few minutes.
- Use the current URL:
https://mcp.zapier.com/api/mcp/mcp. Older setups use the SSE endpointhttps://mcp.zapier.com/api/mcp/sse; it still answers, but preferhttps://mcp.zapier.com/api/mcp/mcpwith clients that support Streamable HTTP. - Check the API key. Zapier expects a key from your Zapier account, usually sent as an Authorization header. A 401 in your client means the key is missing, wrong or revoked; create a new one and update the client config.
- Check the network. VPNs, company proxies and firewalls can block
mcp.zapier.com. Try another network to rule it out. - Update the client. Older clients only speak stdio or the old SSE transport. Current Claude, ChatGPT, Cursor and VS Code versions support remote servers over HTTP.
- Test it outside your client. Paste the URL into our MCP Server Tester to see exactly what the server answers.
Add Zapier MCP to your client
Claude (claude.ai, desktop): Customize, Connectors, + Add, Add custom connector, paste https://mcp.zapier.com/api/mcp/mcp. Claude Code: claude mcp add --transport http zapier https://mcp.zapier.com/api/mcp/mcp. Cursor: { "mcpServers": { "zapier": { "url": "https://mcp.zapier.com/api/mcp/mcp" } } }. VS Code: { "servers": { "zapier": { "type": "http", "url": "https://mcp.zapier.com/api/mcp/mcp" } } }.
Status of the other servers: MCP server status overview.
How it works
- Check the live status Up, including HTTP 401, means the server answers.
- Use the current URL https://mcp.zapier.com/api/mcp/mcp
- Reconnect Remove the connector, add it again and sign in.
FAQ
Is Zapier MCP down right now?
The live check at the top of this page tests https://mcp.zapier.com/api/mcp/mcp at most every five minutes. Up, including HTTP 401, means the server is answering.
What is the Zapier MCP server URL?
https://mcp.zapier.com/api/mcp/mcp. The older SSE endpoint is https://mcp.zapier.com/api/mcp/sse.
Why is Zapier MCP not working in Claude or Cursor?
Most often an expired or revoked sign-in, an outdated URL or a blocked network. Remove the connector, add it again with the current URL and sign in again.
Why does Zapier MCP return 401?
Without a valid token every request gets 401, which is how the client knows it has to sign in. If you see 401 after signing in, the token expired or was revoked; reconnect.