How to Automate Restaurant Email Marketing: From someone who has done it 17 times
How to automate restaurant email marketing: the campaigns to switch on, a two-agent Square and Mailchimp setup, and what it returns in covers and hours
The ad that converts is rarely the 1st you run. It is often the 7th iteration: a sharper opening line, a new angle, or a cut that shows the product in the first two seconds. Teams that test more versions find their winners sooner. And a winning ad keeps selling every day it runs.
Most creative teams never reach version seven. One product video means a shoot, an editor and a week of revisions, so the test runs with two versions. The budget goes behind whichever looks better, and the hook that would have won never gets made.
Ideas for creatives are rarely the bottleneck. Production is. Every new angle costs another edit, so the number of ads you can test is capped by the hours it takes to make them.

Claude and Higgsfield workflows lift that cap. Claude turns a product page into angles, hooks and scripts, and Higgsfield's Marketing Studio turns a product link into video ads. Ad Multiplier then builds variants of the concepts that win. More versions reach the test, and your ad budget moves to the ones that convert.
Connecting is the easy part. The value comes from what sits around it: Claude skills that write on-brand briefs, a person who approves concepts before credits are spent, and a pipeline that ships the winners. We build those skills and workflows for marketing teams.
Check these four things first. Each one is a common reason the setup stalls.
Add the connector once on claude.ai or in Claude Desktop. Remote connectors live in your Claude account, so the same connector is then available in Desktop, Cowork and the mobile apps.
Step 1. Open Connectors. On claude.ai or in Claude Desktop, go to Customize, then Connectors (Or plugins). This depends on what service you’re on.
Step 2. Add a custom connector. Click + Add, then Add custom connector.
Step 3. Enter the details. Name it Higgsfield, paste the server URL https://mcp.higgsfield.ai/mcp and click Continue. Keep the detected sign-in settings, click Continue again, then click Add.

Step 4. Connect and authorize. Click Connect, and a Higgsfield window opens for you to sign in and approve access. If you are already signed in at higgsfield.ai, this step completes on its own.

Step 5. Test it in a new chat. Open a new conversation, click + at the lower left, choose Connectors and make sure Higgsfield is on. Then ask: "Check my Higgsfield credit balance and list the video models I can use."
The connector gives Claude more than raw generation. Higgsfield's MCP overview lists Marketing Studio, which turns a product link into video ads, plus Ad Multiplier and Genjutsu for motion transfer and restyling. It also covers Soul characters, Higgsfield Audio, credit checks, the Asset Library and an upload window for reference images you want to attach.
Claude reaches all of these through tools, so you can ask in plain language and describe the scene, like a woman unboxing your product. A simple trick: name Higgsfield in your first prompts until Claude picks the right tool for each task on its own.
Claude Code has no Connectors menu of its own, so you cannot add the connector from inside it. Some setup posts send Claude Code users to Settings and Connectors anyway, which is the claude.ai path. You have three working options instead.
This is the route Higgsfield documents in its CLI help article for Claude Code and other coding agents. Run three commands:
npm i -g @higgsfield/cli
higgsfield auth login
npx skills add higgsfield-ai/skillsThe login command opens a browser for sign-in. You can also paste Higgsfield's setup message into Claude Code and let it run the commands for you.
The last command uses skills, Vercel's open-source installer for agent skills, not an Anthropic tool. It asks which skills and agents to set up, then writes the skill files to disk in your project's .claude/skills folder, or for every project with the -g flag.
I prefer using the Claude Code integration more than Cowork as I find the depth of iteration that Code provides produces better videos.
If you already added Higgsfield on claude.ai, Claude Code can use it. The Claude Code MCP docs say connectors from claude.ai appear automatically when you log in with a Claude subscription. Finish the Higgsfield sign-in on claude.ai first, then run /mcp to see it.
This does not work when Claude Code runs on an API key or a cloud provider such as Amazon Bedrock. In that case, use the CLI.
Claude Code can also add any remote MCP server directly. Higgsfield does not document this route, so treat it as a fallback:
claude mcp add --transport http higgsfield https://mcp.higgsfield.ai/mcp
Then run /mcp inside Claude Code and sign in through the browser. Add --scope user to the command to make Higgsfield available in every project.

Pick by where you work. The diagram shows the three main routes, and the table adds the admin and non-Claude options

Connecting is free on the Claude side, but generating is not. Higgsfield's help center says an active paid subscription is required. It also says every generation through a connected agent deducts credits "regardless of your plan."
That last part surprises people on unlimited plans. Unlimited access and free generations apply only on higgsfield.ai, not when Claude generates for you.
Because each request spends real credits, set limits before you run batches:
Credit prices per model change often, so check Higgsfield's pricing page rather than numbers quoted in third-party posts.
Once Higgsfield is connected, it is tempting to send a plain prompt for videos and see what comes back. That burns credits on concepts nobody approved. A better pattern puts Claude's planning and a human decision ahead of every expensive step.
The workflow below is a recommended pattern. It combines Higgsfield with the kind of Claude skills and automation we build for marketing teams.
Step one is where Claude earns its place. The open-source Copywriting skill covered in my guide to real Claude skills for marketing turns a product page into angles, hooks and scripts. The Paid Ads skill in the same guide audits where ad spend is leaking, all before any credits move. Ask Claude for a shot list too, so the video model gets context: composition, timing, camera pushes like a slow push in, and each shot's end frame.
Step four uses Higgsfield's marketing tools. Marketing Studio builds video ads from a product link. Ad Multiplier and the Hook Multiplier skill turn a winning concept into related videos, such as a new opening hook with the rest unchanged.
Step five keeps the words around the creative on-brand. Our Claude Humanizer skill cleans captions and scripts so they do not read as machine-written.
Step six can run through an approval flow like my n8n social media automation workflow, which sends every post in one approval email and publishes nothing until a reviewer clicks Approve. Teams that work in Cowork can apply the approval ideas from our Claude for small business guide in the same way.
One rule applies throughout. Higgsfield says you are responsible for anything an agent generates through your account, so keep a person reviewing claims, likenesses and brand use.
How to connect Higgsfield to Claude takes a few minutes. Use a custom connector on claude.ai, Desktop or Cowork, or the CLI in Claude Code, with the mcp.higgsfield.ai URL and a paid plan.
The work that pays off is what you build around it. Claude skills write the brief, people approve before credits go out, and a pipeline ships what wins. If you want that built for your team, we build custom Claude skills and creative workflows for marketing teams.
We build custom Claude skills and creative workflows for marketing teams: on-brand briefs and hooks, approval steps before credits are spent, and pipelines that ship the winners.
• Custom Claude skills for paid ads, copy and brand voice
• Approval gates before any batch generation
• Pipelines from brief to published post, like our n8n social workflow
• From the team behind Real Claude Skills for Marketing
Most failures trace back to a short list of causes. The table explains each error, its likely cause and the fix, drawn from Higgsfield's help center and Anthropic's docs.
The clearest example is public. In GitHub issue #321 on Anthropic's claude-ai-mcp repository, a user's connection attempt failed with "Couldn't reach the MCP server." They had entered https://higgsfield.ai/mcp.
A repository maintainer found that higgsfield.ai did not expose the OAuth discovery details Claude looks for and called it a configuration gap on Higgsfield's side. They asked for the URL Higgsfield documents and closed the issue as not planned.
The fix is the documented server address, https://mcp.higgsfield.ai/mcp, with mcp. at the front. The higgsfield.ai/mcp address is Higgsfield's product page about MCP, not the server itself.
Open Customize, then Connectors in claude.ai or Claude Desktop. Add a custom connector named Higgsfield with the URL https://mcp.higgsfield.ai/mcp, click Connect and sign in to Higgsfield. In Claude Code, install the Higgsfield CLI and run higgsfield auth login.
No. Higgsfield requires an active paid subscription to connect an agent, and the free generations on higgsfield.ai do not apply through Claude. On the Claude side, even the Free plan can add one custom connector.
Yes. Every image or video generated through Claude deducts Higgsfield credits, even on plans that are unlimited on higgsfield.ai.
No. The connector uses OAuth, so you sign in to Higgsfield in a browser window and approve access. There is no key to copy or store.
Higgsfield lists more than 30 image and video models. As of October 2026 its pages name Nano Banana Pro, Soul, Seedance, Kling, Veo 3.1, Sora 2, Flux 2, Seedream 5 and GPT Image 2. The lineup changes often, so check Higgsfield's CLI page or its model pages for the current list.