Langflow 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: MCP Tools component
Setup
Mode: HTTP/SSE
Name: agent-update
MCP URL: https://api.tryagentupdate.com/v1/mcp
Headers: Key = Authorization Value = Bearer au_live_...Before you file a bug
This one is form-based, so there is no pasteable JSON to hand a user, and it is unconfirmed whether the separate JSON mode accepts a Claude-style headers object. The transport is negotiated rather than chosen — Streamable HTTP with an SSE fallback — so there is no field to set. Global variables are explicitly endorsed for header values, and that is the right way to keep the PAT out of the flow. Treat the field labels above as approximate. They were not verified against a current build.
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.