Content production for Series A demo.

Operator-driven content pipeline. Higgsfield generates, Claude routes prompts, you approve, the studio publishes. Every piece tagged to the page or surface it lands on.

Higgsfield account: not connected 4-week production schedule

Production progress

of — pieces

Backlog—

In Higgsfield—

Downloaded—

Imported—

Live on site—

Blocked—

Higgsfield Account

read from your saved connection

edit →

Claude Code × Higgsfield MCP

one-time install — Higgsfield calls become first-class tools in Claude Code

not yet installed

Run this in your terminal

claude mcp add --transport http higgsfield https://mcp.higgsfield.ai/mcp

OAuth via Clerk · same identity as your browser session

What this unlocks: when you queue a piece below and click Send to Claude Code, Claude calls Higgsfield directly via MCP — generates the asset, downloads it, and posts it to the studio. No copy-paste loop.

Endpoint https://mcp.higgsfield.ai/mcp · OAuth 2.1 + PKCE · scopes openid email offline_access

Higgsfield capabilities

what each model is for · pick the right one per piece

Content matrix

every piece needed for the demo · click any row to expand the prompt

Status	Title	Model	Spec	Target	Actions

Pipeline

drag items by changing status — head to Live when published

claude-code · higgsfield-mcp · series-a-assistant idle

Quick prompts