n8n + MCP + BattleBots Request Flow

n8n + MCP + BattleBots Request Flow A sequence diagram generated by Archify. Who are the BattleBots competitors? Analyze prompt / plan Invoke tool: list-battlebots Connect (streamable HTTP) CreateClient BattleBotsApi HttpClient GET /battlebots 200 OK competitor list Stream tool result Tool output (competitor names) Draft final message Answer with competitor list Prompt + planning MCP + HTTP round trip Result + answer User · human · Sequence participant User human AI Agent · n8n · Sequence participant AI Agent n8n Ollama · llama3.1:8b · Sequence participant · Ollama Ollama llama3.1:8b BattleBots Tool · MCP httpStreamable · Sequence participant BattleBots Tool MCP httpStreamable MCP Server Host · Microsoft MCP SDK · Sequence participant MCP Server Host Microsoft MCP SDK Client Factory · IHttpClientFactory · Sequence participant Client Factory IHttpClientFactory BattleBots API · ASP.NET Core Minimal API · Sequence participant BattleBots API ASP.NET Core Minimal API Legend request return default message

Happy Path

  • • User question flows n8n agent -> Ollama -> MCP tool -> API
  • • Return messages are quieter than forward calls
  • • Activation bars show how long each component is busy

MCP Transport

  • • The n8n tool speaks streamable HTTP to the MCP server host
  • • Microsoft MCP SDK builds the request via IHttpClientFactory
  • • The competitor list streams back as the tool result

LLM Orchestration

  • • llama3.1:8b decides to invoke list-battlebots
  • • Tool output returns to the model before drafting
  • • The agent, not the tool, answers the human user