Zapier MCP Server

Zapier MCP is a remote, provider-hosted Model Context Protocol server that exposes Zapier's automation platform to AI agents. Instead of building one-off integrations against each SaaS API, you point an MCP client (Claude Desktop, Cursor, Windsurf, VS Code, ChatGPT, etc.) at your Zapier MCP endpoint and the agent gains the ability to invoke any Zapier action across 8,000+ connected apps including Gmail, Slack, Google Sheets, HubSpot, Salesforce, Jira, Asana, GitHub, Discord, and many more.

Unlike a typical MCP server with a fixed tool list, Zapier MCP is configured per user. You go to mcp.zapier.com, create a server, and add the specific Zapier actions you want to expose (for example "Gmail: Send Email", "Slack: Send Channel Message", "Google Sheets: Lookup Row"). Those become the tools your AI client sees. Zapier handles authentication, encryption, and rate limiting centrally so the agent never touches third-party credentials. The server now uses streamable HTTP transport; legacy SSE endpoints are being phased out.

MCP usage runs on your existing Zapier subscription and consumes two tasks per action call. There is no separate product, contract, or procurement. Two authentication modes are available: API Key (best for personal use and local development) and OAuth (best for apps where end users connect their own Zapier accounts).

Tools

Prerequisites

• A Zapier account (free or paid). MCP action calls consume your existing task quota at 2 tasks per call.
• An MCP-compatible client that supports streamable HTTP (Zapier no longer supports SSE servers).

Step 1: Create your MCP server

1. Go to mcp.zapier.com.
2. Click New MCP Server and select the AI client you plan to use (Claude, Cursor, ChatGPT, etc.).
3. Name your server.

Step 2: Add tools (Zapier actions)

1. Click Add tool.
2. Search for an app (for example Slack, Gmail, Google Sheets, HubSpot).
3. Pick the action you want the agent to call.
4. Authenticate the app account if prompted.
5. Configure default field values and save.

Repeat for each action you want exposed.

Step 3: Connect your client

In the Connect tab, Zapier generates a per-server URL and shows client-specific instructions. The endpoint looks like:

https://mcp.zapier.com/api/mcp/s/<your-server-id>/mcp

For Claude Desktop, edit claude_desktop_config.json (Settings → Developer → Edit Config) and add:

{
  "mcpServers": {
    "zapier": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.zapier.com/api/mcp/s/<your-server-id>/mcp"
      ]
    }
  }
}

Restart the client. Treat the server URL as a secret: anyone with it can run your configured actions.

Step 4: Verify

Ask your agent: "What tools do I have available?" It should list the Zapier actions you added.

Authentication

• API Key: generate one at mcp.zapier.com. Best for personal/local use.
• OAuth: preferred for apps where end users connect their own Zapier accounts.

• Send drafted emails, Slack messages, or SMS from an AI agent without wiring up each provider's API
• Log meeting notes or call summaries to Google Sheets, Notion, or Airtable after a conversation
• Create or update CRM records (HubSpot, Salesforce, Pipedrive) directly from chat with the agent
• Open Jira/Linear/Asana tickets from bug reports the agent receives or generates
• Trigger multi-step Zaps as a single agent action to orchestrate cross-app workflows

• "Send a Slack message to #launches summarizing this release note and email the same summary to the marketing list."
• "Find the HubSpot contact for jane@acme.com and add a note that we demoed the new dashboard today."
• "Append a row to my 'Inbound Leads' Google Sheet with the name, company, and source from this email."
• "Create a Jira ticket in the GROWTH project titled 'Onboarding drop-off on step 3' with the description I just wrote."
• "Look up the last 5 deals in HubSpot owned by me and post them as a table in my Slack DMs."

• Officially built and hosted by Zapier, no self-hosting or infra to manage
• Massive integration surface: 8,000+ apps and 30,000+ actions through one server
• Credentials live in Zapier, so the agent never sees third-party API keys
• Included in existing Zapier subscriptions with no separate contract; per-action approval and activity logs are built in

• Tools must be manually added one by one in the Zapier UI; the agent only sees what you pre-configure
• Each action call consumes 2 Zapier tasks, which can get expensive at high volume
• Single-action focused; complex multi-step orchestration is better handled by Zapier Zaps or Agents, not MCP
• SSE transport is deprecated, so clients must support streamable HTTP

• Composio MCP for a similar multi-app tool aggregator with hosted auth
• Pipedream MCP which exposes thousands of integrated apps as MCP tools
• n8n self-hosted, with community MCP integrations for workflow automation