Skip to main content

Watch the walkthrough

Copy the group chat setup prompt

Paste this into GrokBot to define the team, learn from your existing videos, and agree on the process before generating anything.
Here, DR means direct-response advertising. Review the proposed team and prompting rules before approving the first generation. Learning from previous results helps refine the process; it does not guarantee that every generation will be usable.

Connect StefanBrain to GrokBot

Set up MCP for StefanBrain tool access and computer use for working in the Video workspace and editor.
1

Add the StefanBrain MCP connection

In a GrokBot chat, paste:
Complete the StefanBrain sign-in and review Allow access. You need an active StefanBrain plan or trial. See the StefanBrain MCP setup guide for authentication options and troubleshooting.Use the product endpoint above—not https://docs.stefanbrain.com/mcp, which only provides documentation.
2

Sign in on GrokBot's computer

Ask GrokBot to open the app:
Open the computer preview in GrokBot’s right-hand panel, take control, and complete sign-in. Enter passwords and verification codes in the browser, not in chat.MCP authorization and browser sign-in are separate. Connecting one does not sign you into the other. GrokBot’s computer session is shared across your bots, so only sign in to accounts you want them to use. See GrokBot’s computer-use guide for taking control and handling sign-in.
3

Check both before setting up the group

If MCP cannot connect, follow the MCP setup guide. If the browser shows a login screen, take control and sign in there again.
Use MCP for interactive work with your assistant. For unattended pipelines or machine-scale generation, use the Developer API.

Set up a small production team

Create the group in GrokBot, not inside StefanBrain. Create a group with clear responsibilities: You can begin with fewer roles. What matters is that someone owns each handoff and that the team knows when to stop and ask you.

Give the team a clear brief

Include your product, audience, offer, creative direction, and references. Share examples of previous videos you liked and explain what worked: the opening, delivery, character, pacing, or product demonstration. Ask for ideas before spending video allowance. For example:
Once you choose a concept, give the team a concrete delivery target:

Choose the style and format before generating

Use StefanBrain’s Video workspace to choose the Style, Format, duration, and aspect ratio. Attach the correct Product and any visual references. Keep the prompt focused on the scene and message instead of packing it with unrelated instructions. For a song ad, agree on the song direction and product pronunciation before generating. For a recurring character, reuse the same references so later clips have a clearer visual target. See how to prompt product videos for the generation setup and create AI song ads for the song workflow.

Review the result before adding more edits

Have QA watch the entire video, then bring you a short list of concrete issues:
  • Is the product name pronounced correctly?
  • Does the opening match the concept you approved?
  • Are the product and character consistent between scenes?
  • Do the spoken claims match the product information?
  • Can you follow the message without distracting overlays?
Keep the review practical. In the walkthrough, too much B-roll covers the original creative. An extra overlay is only useful when it makes the message easier to understand.

Fix the weak spots without rebuilding everything

Open the generated video in StefanBrain’s Video Editor. Use a focused dialogue edit for a mispronounced line, compare another hook when the opening needs work, and add captions or B-roll only where they improve the video. Review the displayed usage cost before generating new takes. After an edit, replay the surrounding scene to check that the change still fits. Follow edit hooks, dialogue, and captions for the individual controls. For a multi-clip piece, the walkthrough also uses an external editing workflow to assemble clips and add audio. That assembly is separate from StefanBrain’s native Video Editor. Check transitions, audio levels, and caption consistency across the finished piece.

Keep what worked for the next brief

Save the approved prompt, references, chosen settings, and the edits that improved the result. Give the team specific feedback—such as “keep the character visible during the hook”—so future runs can reuse a useful rule instead of repeating the same mistake. Review the finished video yourself before using it in an ad. Increase autonomy only after the workflow reliably produces work you would approve.

Practical use cases

Choose a concept before spending video minutes

Ask for 10 distinct concepts, compare the hooks and visual directions, then approve one for generation.

Fix a product-name pronunciation

Have QA identify the exact line, let the Editor propose a replacement, and compare the new take before keeping it.

Assemble a consistent multi-clip ad

Reuse character references across clips, then check transitions and caption consistency in the assembled video.