Zapier

{
  "mcpServers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zapier.com/api/mcp/mcp"
      ]
    }
  }
}

Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.zapier.com/api/mcp/mcp. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

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

Then run /mcp inside Claude Code to finish the sign-in. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

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

Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "servers": {
    "zapier": {
      "type": "http",
      "url": "https://mcp.zapier.com/api/mcp/mcp"
    }
  }
}

VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "mcpServers": {
    "zapier": {
      "serverUrl": "https://mcp.zapier.com/api/mcp/mcp"
    }
  }
}

Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "mcpServers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zapier.com/api/mcp/mcp"
      ]
    }
  }
}

Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "streamable-http",
          "url": "https://mcp.zapier.com/api/mcp/mcp"
        }
      }
    ]
  }
}

Continue takes the hosted URL directly in the transport block. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

codex mcp add zapier --url https://mcp.zapier.com/api/mcp/mcp

Codex detects OAuth support and opens the browser to authorize. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "context_servers": {
    "zapier": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://mcp.zapier.com/api/mcp/mcp"
        ]
      }
    }
  }
}

Bridged through mcp-remote under "context_servers". Settings live-reload on save. This endpoint expects an API key, usually as an Authorization header — set it where your client configures headers (mcp-remote: add --header "Authorization: Bearer <key>").

{
  "name": "Zapier",
  "transport": "http",
  "url": "https://mcp.zapier.com/api/mcp/mcp"
}

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.