Higgsfield MCP: server URL, setup, and what it costs

Higgsfield MCP is Higgsfield's remote MCP server at https://mcp.higgsfield.ai/mcp. You add that URL to Claude or another MCP client, sign in with your Higgsfield account instead of an API key, and each image or video it makes costs credits from your Higgsfield plan, priced by model and resolution.

Every Higgsfield fact here comes from its MCP page and the MCP FAQ on its CLI page, read on 2026-09-28. Sume has no connection to Higgsfield's server. For how the two platforms compare overall, see Sume vs Higgsfield.

How do I connect Higgsfield MCP?

Higgsfield's MCP page has setup tabs for Claude, ChatGPT, Claude Code, CLI, and Other. Its FAQ gives the general rule: add the Higgsfield MCP server URL in your agent's settings and authenticate through your Higgsfield account.

• Claude: the Claude tab has a Connect Higgsfield button and the server URL, https://mcp.higgsfield.ai/mcp.
• ChatGPT: the ChatGPT tab has an Install Higgsfield plugin button, with the same URL shown.
• Claude Code: this tab sets up the Higgsfield CLI rather than the MCP URL. It has you run npm i -g @higgsfield/cli, then higgsfield auth login to sign in through the browser, then npx skills add higgsfield-ai/skills for the companion skills.
• Other clients: the FAQ says any MCP-compatible client can connect by pointing it to the Higgsfield MCP server.

Is Higgsfield MCP free?

Connecting needs no API key, but every generation spends credits. Higgsfield's FAQ says its tools use the same credit system as the Higgsfield platform, each generation costs credits based on the model and resolution, and your existing plan credits work through any connected agent. The MCP pages read for this post name no separate MCP price, so what a generation costs depends on your Higgsfield plan and the model you pick.

What can Higgsfield MCP do?

The FAQ answers the common questions about capabilities:

How does another media MCP server handle auth and billing?

Other remote media servers make different choices. Sume's hosted MCP server at https://mcp.sume.com/mcp is one example, per its MCP overview and OAuth and API keys docs. Sume basics says hosted MCP still works but is not the primary path today.

• Auth: OAuth sign-in starts read-only (mcp:read); turning Write on at consent adds mcp:write and exposes paid tools. A Sume API key sees the full hosted tool set.
• Billing: paid generation uses Sume USD estimates. The estimate is reserved from the workspace balance at submit and captured on success; failed jobs release or refund it where applicable (Generation admission).
• Tool names differ. If a prompt or skill written for Higgsfield calls get_workflow_instructions, models_explore, media_import_url, or remove_background, Sume's tools docs say those names are not in its tools_list; cutouts there are rmbg_create.
• Setup and per-call spend controls are in Connect Claude Code, Cursor, or Codex to Sume.