<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/e98719cb3caa4a68ad532d0c73f3523b&quot; frameborder=&quot;0&quot; width=&quot;3376&quot; height=&quot;2532&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2532</height><width>3376</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2532</thumbnail_height><thumbnail_width>3376</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e98719cb3caa4a68ad532d0c73f3523b-0734af23986758d3.gif</thumbnail_url><duration>122.816667</duration><title>Trigger scenarios with MCP Toolboxes and Scenario Inputs</title><description>This Loom explains how to use MCP Toolboxes with Cloud to trigger scenarios using scenario inputs. The speaker demonstrates setting up a toolbox connected to Cloud where tools correspond to scenarios, starting with a start scenario module that waits for required scenario inputs. They note that this approach avoids copy pasting and that Cloud can recognize and provide the input when triggering via mcp2boxyteracle, enabling the scenario to run with that data. The setup is described as adding a start scenario at the beginning of an existing working scenario and defining inputs, such as a required script text field.</description></oembed>