Open WebUI 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: Admin Settings -> External Tools -> + Add Server
Setup
Type: MCP (Streamable HTTP)
URL: https://api.tryagentupdate.com/v1/mcp
Auth: None
Headers: {"Authorization": "Bearer au_live_..."}Before you file a bug
Use the free-form Headers field and set Auth to None. Do not use Bearer mode. The Headers field is the only route where the Bearer scheme is unambiguous. Bearer mode's Key field probably takes the raw token, but the docs never say so, and guessing costs you a 401. v0.6.31 is the minimum version, and from there on the old mcpo proxy is no longer needed. Template variables such as {{USER_EMAIL}} inside MCP headers are sent as literal strings (issue #21184, unresolved), and ENABLE_FORWARD_USER_INFO_HEADERS does not reach MCP tool servers. Neither matters for a static bearer; both block per-user tokens.
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.