Skip to content

Summary

Zapier's official hosted MCP server, exposing actions across 8,000+ connected apps as agent tools — with you choosing exactly which actions each server may perform.

Features

  • Actions across 8,000+ Zapier-connected apps as MCP tools
  • Per-server action allowlists — you pick exactly what an agent may do
  • Separate connection token per MCP server for scoped permissions
  • Hosted endpoint at mcp.zapier.com/api/v1/connect
  • OAuth browser sign-in or bearer token authentication
  • Guided setup for ChatGPT, Claude, Cursor, VS Code, Windsurf and Copilot Studio

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Zapier MCP" tools will be available.
{
  "mcpServers": {
    "zapier-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zapier.com/api/v1/connect",
        "--header",
        "Authorization: Bearer ${ZAPIER_MCP_TOKEN}"
      ],
      "env": {
        "ZAPIER_MCP_TOKEN": "your-connection-token"
      }
    }
  }
}

Description

Zapier's value has always been that it already holds authenticated connections to nearly every SaaS product a company uses. Zapier MCP turns that estate into tools an agent can call, which is a materially different proposition from wiring up individual MCP servers one integration at a time: one connection, and Gmail, Slack, HubSpot, Google Sheets, Notion, Jira and thousands more become available without a separate OAuth dance for each.

The scoping model is the important detail. You do not hand an agent all 8,000 apps. At mcp.zapier.com you create a named MCP server and choose the specific actions it may take — "send a Slack message to #alerts", "append a row to this sheet", "create a HubSpot contact". Each server gets its own connection token. That means a research agent and a deployment agent can hold genuinely different permissions, and the blast radius of a misbehaving prompt is bounded by a list you wrote rather than by the model's judgement.

Connection: the hosted endpoint is https://mcp.zapier.com/api/v1/connect. The setup portal generates a client-specific configuration for ChatGPT, Claude, Cursor, VS Code, Windsurf, Microsoft Copilot Studio or a generic client.

Authentication: OAuth is the smoothest path — the first connection opens a browser to sign in and authorise, then the credentials are reused. Alternatively, generate a connection token and send it as Authorization: Bearer <token>, or pass it as a query parameter on the server URL. Copy the token when it is generated; it is not shown again.

Good for: agents that need to act in business systems rather than only read from them — filing tickets, updating a CRM, posting notifications, moving records between tools — where standing up and maintaining a separate MCP server per product is not worth the effort.

Worth knowing: actions run through Zapier and count against your Zapier plan's usage, so the pricing and rate characteristics are those of your Zapier account, not of a standalone server.

Related MCP Servers

Featured

Official instance-level MCP server that lets AI agents discover, run, and edit workflows on your n8n instance.

Trigger.dev's official MCP server — trigger and monitor background jobs, deploy to any environment, and query runs with TRQL from your coding agent.

MCP: Dagster+ MCP Server

by Dagster Labs

Dagster Labs' official remote MCP server for Dagster+: inspect assets, runs, run logs and Insights metrics, and launch runs from an AI session.

Browse all MCP servers →