Zapier talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.
Where it goes: Apps -> + Add connection -> MCP Client -> Connect an Account
Setup
Server URL : https://api.tryagentupdate.com/v1/mcp
Transport : Streamable HTTP
OAuth : No ← MUST be No
Bearer Token : au_live_... ← raw token (inferred)Before you file a bug
Selecting OAuth = Yes silently discards the Bearer Token. It is the number one misconfiguration here, and the symptom is a connection that looks saved and 401s on every call. Zapier exposes exactly one credential field and no arbitrary-header UI. Fine for Agent Update, impossible for any server that needs a second header or a tenant id. An auth tab still opens at step 7 with nothing to do on it, so warn people before they hunt for a missing field. Rename the connection to include "Agent Update" — Zapier's own advice, and it matters once you have several. This is a beta feature. Whether the field wants the raw token or the full header value is inferred from the label and the OAuth interaction, so if au_live_... alone 401s, try Bearer au_live_... next. Once connected, the tools show up as Action → "Run Tool" for send_message and ask_question, and Search → "Run Read-Only Tool" for check_replies.
Check it worked
Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.
Next
The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.