Higgsfield MCP + Claude: the animated-site tutorial

The video opens with finished examples, so the eye sees the goal before the method.

• What happens. Four or five sites scroll past: a melted-photo hero, a dark dancer site, an astronaut scene, a portrait statement page. Video plays in the background of each. All work on a phone.
• Why it matters. Every one of these was built by Claude, not by a designer hand-animating frames. The showcase sets the bar before explaining the method.

• What happens. Get the Claude desktop app, open the Code tab, start a new session in a new folder. Pick the strongest model for site work (Fable 5). First prompt: a hero section, white background, centred text, no gradients, black and minimal, plus "install the MCP".
• Why it matters. A plain, honest starting screen is easier to judge and to build on than an overloaded first prompt. The MCP request in the same first message is what wires in the image tool for everything after.

• What happens. Instead of making images on Higgsfield's own site and pasting them in, he connects Higgsfield straight into Claude. Go to higgsfield.ai/mcp, open the "Claude Code" tab, copy the setup block, paste it to Claude. Claude adds the MCP server, sign-in finishes in the browser, then he installs the companion skills with npx skills add higgsfield-ai/skills (the skills repo). Claude confirms it is authenticated.
• Why it matters. The image tool moves into the same conversation as the code. No more tab-switching, downloading, re-uploading. Claude can ask for an image, get it, and place it, in one loop.

• What happens. For the scroll animation, he does not describe it loosely. He takes a screenshot of a page he likes and pairs it with a written spec, a full pixel-faithful recreation prompt, then tells Claude "under our hero section add this thing". We kept his exact spec: the NovaAI recreation prompt.
• Why it matters. A loose request ("make it feel cinematic") gets a loose result. A written contract, exact URLs, a do-not list, an acceptance check, gets the same page back every time. It is the same discipline we use for BPA-faithful mockups.

• What happens. The prompt: "generate a couple of futuristic architecture images using Higgsfield MCP, use 4K quality highest resolution and use GPT-2 image model in this style", plus one image picked from a Pinterest search. He picks the pin with the most likes, his reasoning: what an audience already likes most is a good bet for what a client will like too.
• Why it matters. One style image anchors every generated picture to the same look. Without it, each new image drifts to its own style and the site stops feeling like one thing.

• What happens. The finished gallery scrolls through, every image in the same unified style. He checks the mobile view. The hero section is done, his words, "in less than five minutes". He then moves on to asking the AI to build the rest of the pages.
• Why it matters. His own line: "the most important thing whenever you're building a website, it needs to be united." Speed only counts if the result still holds together as one piece.