brainax

MCP in plain words

Lesson 16 of 22 in the course “AI Video, No Flops”. Free, with animations and a quiz.

One plug for every tool

Until this level Mira did everything by hand: open Higgsfield, paste the prompt, wait, download, repeat. Now let’s bring in a helper. An AI agent is a chat model like Claude or ChatGPT that can not only answer but also press buttons in other services by itself. For an agent to work with a service, the two have to be connected. That’s what MCP (Model Context Protocol) is for: an open standard Anthropic introduced in November 2024. Its creators compare MCP to a USB-C port: one plug that fits any device. A service builds its MCP once, and it can be connected to any agent that supports the standard.

What happens inside

The loop is always the same. Mira writes the task in plain words: “make three drafts of shot 2 from the storyboard”. The agent decides which tool it needs and writes the prompt by the rules we covered: shot, camera, light, motion. The tool generates the video and charges credits. The agent shows the result, and Mira decides what’s next. The key point: the agent isn’t magic. It writes prompts the way you do, just faster and without getting tired. If it doesn’t know the rules of directing and physics, the prompts will be weak. So everything you learned in earlier levels now becomes instructions for the agent.

Higgsfield’s official MCP

Higgsfield has an official MCP server at mcp.higgsfield.ai/mcp. You add it as a connector in Claude, ChatGPT or Cursor and log in with your Higgsfield account. After that the agent can generate images and video straight from the chat, and on 9 June 2026 Kling Motion Control was added to the MCP too, the tool we covered in the lesson on motion transfer. Generations come out of your account’s credits, so the agent spends your money, not its own. There are others nearby: Runway, HeyGen and fal.ai also offer MCP or APIs for agents. The logic is the same everywhere; only the models and prices change.

Why an agent at all

One shot is easier by hand. An agent pays off on a series. In a 15-second ad Mira has five shots, three drafts each, plus versions for different formats. By hand that’s dozens of identical actions: copy the prompt, change a detail, press, wait, download, rename. Somewhere you’ll slip and paste the wrong reference. The agent takes the shot list, writes prompts by the same rules, runs the batch and files the results into folders. Meanwhile Mira isn’t pressing buttons; she does what only a person can: pick the best takes and decide what to fix.

The agent spends your money

An agent is very eager: ask it to “make it perfect” and it may launch forty 4K generations and burn a month of credits in one evening. So four rules apply from day one. First: a credit cap right in the task. Second: expensive steps like 4K and long shots happen only after your explicit “yes”. Good agent apps can ask for confirmation before each action; don’t switch that off. Third: no API keys or passwords in the chat, only log in through the connector, or the key stays in the chat history. Fourth: the agent keeps a log of what it ran and what it spent, so you can always check the bill.

A brief instead of “make it cool”

“Make a cool sneaker ad” is a bad task for a person and for an agent alike: it will fill in everything itself, and most likely wrong. A good brief fits in five lines. Goal: length, product, platform, format, audience. Hero: a link to the character folder from the lesson on keeping one face, so the agent takes references instead of inventing a look. Shots: which scenes from the storyboard and how many drafts for each. Budget: drafts at low resolution and a credit ceiling. Stop: where the agent must stop and wait for you. Five lines take a minute to write and save hours of redoing.

What the agent won’t do for you

An agent takes away the routine, but four things stay with the person. Taste: the agent can’t feel which take is alive and which looks cringe; you decide that by looking at the grid of drafts. Idea and story: the agent executes a plan well, but deciding why the video exists and what the viewer should feel is your job. Rights: the agent won’t check whether a random passer-by looks like a real celebrity or whether someone else’s logo is in the shot. And the final “publish”: a person, not a model, is responsible for the video in the feed. In the next lesson we’ll build the whole pipeline using an ad one person made in two to three days.

Check yourself

  1. Mira wants Claude to make drafts in Higgsfield straight from the chat. What does she need to do?
    Correct answer: Add the Higgsfield MCP as a connector and log in with her account. An agent works with a service through MCP. The connector gives a safe account login with no keys in the chat.
  2. The agent suggests making 40 videos in 4K right away “for quality”. What should she answer?
    Correct answer: No: low-res drafts within the cap first, 4K only for the chosen ones. Expensive steps come only after choosing. A cap and confirmation protect the budget.
  3. Mira writes to the agent: “Make a cool sneaker ad”. What’s missing?
    Correct answer: A brief: goal, hero with references, shots, budget and a stop point. Five lines of brief give the agent everything it needs to hit the task first time.
  4. The agent generated 15 drafts and scored each one. Who picks the final take?
    Correct answer: Mira: the agent’s scores are a hint, taste and responsibility are hers. The agent takes the routine; a person judges how alive a take is and what posting it means.

← Edits instead of regenerating A pipeline with an agent →