Skip to content
Atomic Agent logo Atomic Agent docs

Zapier MCP with Atomic Agent

Zapier MCP gives an agent the actions of the apps you have connected in Zapier: send a Slack message, add a row to a Google Sheet, create a HubSpot contact, and so on. Zapier holds the app credentials; the agent only gets a connection token for one Zapier MCP server. Atomic Agent connects over Streamable HTTP with that token in a header.

Config

{
  "name": "zapier",
  "description": "Zapier actions",
  "transport": {
    "kind": "streamable_http",
    "url": "https://mcp.zapier.com/api/v1/connect",
    "headers": { "Authorization": "Bearer YOUR_CONNECTION_TOKEN" }
  }
}

Get the token:

  1. Go to mcp.zapier.com and click Add MCP server.
  2. Under Choose your AI agent, pick Other.
  3. Add the actions you want the agent to have.
  4. Open the Settings tab and click Generate token in the API token section. Copy it right away: Zapier shows it once.

Paste the literal token. Atomic Agent sends headers exactly as written and does not expand ${VAR}. Zapier also accepts the token as a ?token= query parameter, but recommends the header because URLs end up in logs more easily.

Where to add it:

  • Desktop app: Settings › Connections › MCP servers › Add server, paste the object, press ⌘Enter (Ctrl+Enter on Windows and Linux), then Restart on the new row.
  • Terminal UI: /mcp add, paste the object. It connects right away.
  • By hand: add the object to mcp.servers in ~/.atomic-agent/config.json and restart the agent.

Use "kind": "streamable_http". Zapier MCP does not support SSE.

What to ask the agent

Tools arrive as mcp.zapier.<tool>, one per action you enabled. Some prompts that work well:

  • “Summarize today’s changes in this repo and post the summary to #eng-updates in Slack.”
  • “Read leads.csv and add each row to the Leads sheet in Google Sheets. Show me the first three before you start.”
  • “Create a Google Calendar event tomorrow at 10:00 called Release review and invite the address in TEAM.md.”
  • “When this test run finishes, send me an email with the failures.”

The pattern: the agent does the local work (reading files, running commands, summarizing) and Zapier delivers the result to another app.

Tokens and approvals

  • Where the token lives. In the header in ~/.atomic-agent/config.json, in plain text, written with owner-only permissions (0600) on macOS and Linux. Zapier’s docs say to treat it like a password: anyone with it can run that server’s actions.
  • Why a connection token, not OAuth. Zapier’s sign-in flow for listed clients is OAuth, which Atomic Agent does not run. The connection token is Zapier’s documented path for other clients.
  • Limit the server, not just the agent. Only add the Zapier actions you actually want the agent to have. A server with “send email” and “delete row” can do both.
  • What asks for approval. Zapier actions that the server does not mark read-only ask before they run, so a Slack post or an email waits for your approval. Do not set trust to pure_read on this server. In the TUI, Ctrl+Y approves one call and Ctrl+F allows the whole category for the session; prefer Ctrl+Y for anything that sends. At approval level 5 (full trust) nothing asks.
  • Rotating the token in Zapier invalidates the old one at once. Paste the new one into the config and press Restart.

Troubleshooting

401 Unauthorized. Token missing, mistyped, rotated, or still a placeholder. Generate or rotate it, paste the literal value, press Restart.

Connected, but the tool you expect is not there. Each action you enable on the Zapier server becomes one tool. Add it at mcp.zapier.com, then press Restart (or R on the row in the TUI) to reload the tool list.

Configured with "kind": "sse". Switch to streamable_http with the URL above.

The model ignores the tools. Many enabled actions mean a long tool list in every prompt, which small local models handle poorly. Keep the server to the few actions you use.

FAQ

Is this the official Zapier MCP?

Yes. It is run by Zapier at mcp.zapier.com and documented at docs.zapier.com/mcp.

Does the agent see my Slack or Google credentials?

No. Zapier keeps the app connections and runs each action itself. The agent only holds the Zapier connection token.

Can several clients share one Zapier server?

Yes, Zapier allows it, but rotating the token then cuts off all of them. One server per client is easier to manage.

Checked on 22 Oct 2026 against Atomic Agent v0.6.10 and Desktop v0.0.4, and Zapier’s connect any MCP client and authentication docs.

Get updates by email

One email when a new version comes out.