Zapier MCP

Connects MCP clients to Zapier's 9,000+ app integrations.

Official
Remote
Streamable HTTP
v1.0.1

Official: the MCP registry verified that the publisher controls the domain zapier.com, which this server's name is under. Source: MCP registry, checked 2026-09-25.

Repository

How to connect

Your client connects to the URL. The first time, it asks you to sign in or, for some servers such as GitHub's, to add a token; the repository's README says which.

Terminal

claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect

~/.cursor/mcp.json

{
  "mcpServers": {
    "zapier": {
      "url": "https://mcp.zapier.com/api/v1/connect"
    }
  }
}

~/.codex/config.toml

[mcp_servers.zapier]
url = "https://mcp.zapier.com/api/v1/connect"

Syntax from each client's docs, checked 2026-09-25: Claude Code, Cursor, Codex.

Details

Official: Yes
Runs: Remote
Transport: Streamable HTTP
Installs from: Not listed
Registry version: 1.0.1
License: MIT
Remote URL: https://mcp.zapier.com/api/v1/connect
Registry name: com.zapier/mcp
Repository: zapier/zapier-mcp

Remote, local, transport and packages are read off the registry's platforms. Sources: GitHub, checked 2026-09-25; MCP registry, checked 2026-09-25.

Maintenance

Counts as checked on the day shown. Not a rating.

8 contributors on GitHub as of 2026-09-25.

Also by Zapier1

Zapier AIToolConnects your apps and automates the steps between them

All 2 by Zapier

Friday

The brief, by email

Five to seven links an issue, each with what to do about it.

Unsubscribe from any issue.

This page as Markdown