Zapier MCP Server (Remote)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "zapier-mcp-server-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zapier.com/api/mcp/a/<your-account>/mcp?serverId=<your-server-id>"
      ]
    }
  }
}

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

• A Zapier account
• A Zapier MCP server URL and API key generated at mcp.zapier.com (or OAuth via mcp.zapier.com/api/v1/connect for multi-user apps)
• Connected app accounts in Zapier for whatever services you want the assistant to act on (e.g. Slack, Gmail, Teams)
• An MCP client that supports remote HTTP MCP servers (Claude, Cursor, etc.)

About Zapier MCP Server (Remote)

Tools & capabilities (10)

When to use it

• Use it when you want an assistant to post to Slack or Microsoft Teams, or send Gmail, without coding each API
• Use it when you need to reach thousands of SaaS apps through one MCP connection
• Use it when you want the agent to discover and enable new actions on demand (agentic mode)
• Use it when you'd rather pre-approve a fixed, governed set of actions (classic mode)
• Use it when building a product where each end user connects their own Zapier account via OAuth
• Use it when you want a hosted integration layer with no server to run or maintain

Quick setup

1. 1Sign in at mcp.zapier.com and generate your personal MCP server URL and API key
2. 2Connect the app accounts (Slack, Gmail, Teams, etc.) you want available in Zapier
3. 3Enable the specific actions you want the assistant to use (or rely on agentic discovery)
4. 4Add the Zapier MCP server URL plus API key to your MCP client's remote-server config
5. 5Restart the client and confirm the Zapier tools appear
6. 6Verify with a low-risk read action, then test a write action like sending a Slack message

Zapier MCP Server (Remote) FAQ