Make → Agent Update

Make 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: HTTP -> "Make a request" module

Setup

URL      : https://api.tryagentupdate.com/v1/agent/messages
Method   : POST
Headers  : Authorization = Bearer au_live_...
           Content-Type  = application/json
Body type: Raw / JSON

Before you file a bug

Ship the REST recipe, not the MCP one. Make does have an MCP Client module — connection → MCP Server = "+ new MCP server" → URL → API Key / Access Token = au_live_... → Save. Those field names are verified; its behaviour is not. Two unknowns make it unshippable as it stands. How Make turns that field into an HTTP header is undocumented: searching the rendered page for "bearer", "authorization" or "header" returns zero hits. And there is no transport selector, and no mention of Streamable HTTP or SSE anywhere. There is no arbitrary-header UI to fall back on either. It is an open beta, and OAuth is what the page actually documents. If you do try it, test with "Call a tool" against check_replies before wiring anything real. If you are not going to test it end to end, publish only the HTTP-module REST recipe above.

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.