Agent Update

Connect

n8n → Agent Update

A self-hostable workflow automation tool that wires apps, APIs and AI agents together on a visual canvas.

n8n 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 Client Tool node (@n8n/n8n-nodes-langchain.mcpClientTool), attached to an AI Agent's Tool port

Setup

MCP Client Tool node
Server Transport : HTTP Streamable
Endpoint         : https://api.tryagentupdate.com/v1/mcp
Authentication   : Bearer Auth
  └ new "Bearer Auth" credential → Bearer Token: au_live_...   ← RAW token
Tools to Include : All
Pasteable node JSON (credential still selected by hand)
{ "nodes": [{ "parameters": {
  "endpointUrl": "https://api.tryagentupdate.com/v1/mcp",
  "serverTransport": "httpStreamable",
  "authentication": "bearerAuth",
  "include": "all" },
  "type": "@n8n/n8n-nodes-langchain.mcpClientTool", "typeVersion": 1.4,
  "name": "Agent Update", "position": [0,0] }], "connections": {}, "pinData": {} }

Before you file a bug

The double-Bearer trap lives here. n8n builds the header itself from Authorization: '=Bearer {{$credentials.token}}', so the Bearer Auth credential takes the raw token. Paste au_live_... and nothing else. That is the exact opposite of Dify and Flowise, so call the difference out if you document both. The MCP Client Tool docs page is stale: it still lists only an "SSE Endpoint" and never mentions "Server Transport". Trust the node in front of you, not the page. typeVersion 1.2 and above defaults to HTTP Streamable, but an older workflow may still be pinned to 1.1 and SSE, so check the dropdown. There is an alternative: set Authentication to "Header Auth" with Name Authorization and Value Bearer au_live_.... In that mode you do type the Bearer prefix yourself.

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.

← All docs