How to Connect Zapier MCP to Slack: Slackbot or a Shared AI Agent (2026)

Two ways to use Zapier MCP from Slack: connect it to Slackbot with Zapier's OAuth connector, or add it to a shared Runbear agent your whole channel can @mention. Steps and limits as of November 2026.

Short answer (as of November 2026): there are two ways to use Zapier MCP from Slack. For a personal assistant, connect Zapier to Slackbot with Zapier's Slackbot connector, which signs you in with OAuth and needs no token. For an agent the whole team shares, add Zapier to a Runbear agent as a Custom MCP server, so anyone in the channel can @mention one agent and have it run your Zapier actions. Both rely on Zapier MCP, which only supports the Streamable HTTP transport, and on Zapier's side each successful tool call uses two tasks from your Zapier plan.

Option A: Connect Zapier MCP to Slackbot

Slack made Slackbot's MCP client generally available on June 17, 2026, and Zapier documents a direct connection for it. You need a Zapier account, a Slack plan that includes Slackbot, and fewer than 5 active MCP servers in Slackbot. A Slack admin may need to turn on Slackbot or approve Zapier first. The steps, from Zapier's Slackbot guide:

  1. In Zapier, connect Slack from your connections page, or reconnect it if it is already connected. Existing connections do not include the MCP permission.
  2. Choose the workspace where you use Slackbot, confirm the permission that lets Zapier connect to Slack's AI features through MCP servers, and click Allow.
  3. Refresh Slack, open Slackbot, and send: "Connect to Zapier MCP for me. If I have not already connected to Zapier, prompt me to install the connector."
  4. Click Connect, then Continue to Zapier, pick your Zapier account, and click Allow. Slackbot confirms that Zapier is connected.

Zapier creates a default MCP server for you during sign-in. Its quickstart says the server pre-enables actions for apps already connected to your Zapier account, so check which actions are enabled in Zapier before you rely on one.

Limits from Slack's developer guide, as of November 2026:

  • Each user can have up to 5 active MCP servers at a time.
  • If the server doesn't return a result within 60 seconds, Slackbot aborts the call.
  • For third-party tools, the user must explicitly authorize each tool call, both read and write.

Option B: Connect Zapier MCP to a shared Runbear agent in Slack

A Runbear agent is also an MCP client, and it lives in your Slack channels as a teammate. Instead of each person connecting Zapier to their own Slackbot, the team @mentions one agent that has its own instructions, knowledge sources, and tools, with Zapier as one of them. Runbear is not on Zapier's list of one-click clients, so the setup has two parts.

Part 1: Create a Zapier MCP server and connection token

Use Zapier's setup for other clients (Zapier docs):

  1. Go to mcp.zapier.com and click Add MCP server. In the agent picker, choose Other.
  2. Open the Settings tab and, under API token, click Generate token. Copy it right away: Zapier shows the token only once.
  3. Note the connection URL, https://mcp.zapier.com/api/v1/connect. Zapier recommends sending the token as a header, Authorization: Bearer <token>, rather than in the URL.

Check which actions are enabled on this server in Zapier. Runbear lists whatever tools the server exposes after you connect it.

Part 2: Add Zapier as a Custom MCP server in Runbear

The steps follow Runbear's Custom MCP guide:

  1. Open your agent in the Runbear dashboard and go to the Tools tab.
  2. In the Custom MCP category, click Add Custom MCP.
Runbear agent Tools tab showing the Custom MCP category with an Add Custom MCP button above the integration catalog
  1. Set Server Name to Zapier, Server URL to https://mcp.zapier.com/api/v1/connect, and Transport Type to Streamable HTTP.
  2. Under Authentication, choose Static. Set Header Key to Authorization and Header Value to Bearer <your Zapier token>.
  3. Click Connect. Runbear performs a handshake with the server and lists the discovered tools on the server tile.
Add Remote MCP Server dialog in Runbear with fields for Server Name, Server URL, Transport Type set to Streamable HTTP, and OAuth, Static, or None authentication

A static header is one credential for everyone who uses the agent, so every action runs as the Zapier account that owns the token. Runbear encrypts header values at rest and doesn't expose them in logs or to end users.

In Slack, the agent always answers @mentions and DMs. Replying without an @mention and triggering by keyword are extra switches you turn on per channel. For a broader look at building a no-code agent for your workspace, see Runbear's Slack integration.

Which path fits your team

  • Choose Slackbot if each person mainly wants to ask Slackbot in their own conversation, with their own Zapier account, and Slackbot's limits (5 MCP servers per user, 60-second calls, per-call approval for third-party tools) are fine.
  • Choose a Runbear agent if you want one agent the whole channel can call, with its own instructions and knowledge next to Zapier, set up once from a dashboard and shared by everyone who uses the agent. The same agent can also run in Microsoft Teams, and Runbear plans are priced by usage rather than per seat.

Keep the Zapier token safe (Option B)

  • Treat the token like a password. Anyone holding it, or a URL containing it, can run tools on your Zapier MCP server and access your data.
  • If it leaks, open the server's Settings in Zapier and click Rotate token. The old token stops working right away, so paste the new one into the Runbear server.
  • Use the Authorization header, as in the steps above, rather than putting the token in the URL.

What you can ask for once it's connected

Whatever actions your Zapier MCP server exposes, the AI can call from a Slack message. For example:

  • "Create a ClickUp task from this thread and assign it to me."
  • "Add this lead to the Google Sheets pipeline tab."
  • "Email this summary to the client through Gmail."

FAQ

Can Slackbot use Zapier MCP?

Yes. Slack made Slackbot's MCP client generally available in June 2026, and Zapier has a Slackbot connector: reconnect Slack in Zapier with the MCP permission, then ask Slackbot to connect to Zapier MCP and sign in with OAuth. You need a Slack plan that includes Slackbot, and an admin may need to approve Zapier.

Does Zapier MCP work with SSE?

No. Zapier MCP supports Streamable HTTP only. In Runbear, leave Transport Type on Streamable HTTP.

How much does Zapier MCP cost per action?

On Zapier's side, each successful tool call uses two tasks from your Zapier plan.

Your first teammate is 10 minutes away.

Add Runbear to Slack, hire an agent in chat, and watch it work. Free to start, no credit card.

Want a walkthrough first? Book 20 minutes with our CEO