Integration profile · Checked September 28, 2026

Higgsfield MCP: Agent Media Workflows, Access and Credits

Higgsfield MCP connects a compatible agent to your existing Higgsfield account for media generation. OAuth links the account; an active paid subscription and standard Higgsfield credits are required. Website Unlimited and free-generation benefits do not carry over.

Source-verified; not independently benchmarked. This is an integration profile, not a review of every model on the Higgsfield website.

What it is — and what it is not

MCP exposes Higgsfield operations to an agent through the Model Context Protocol. It is not an independent generation model, a free generation channel, or the separate Higgsfield REST/API product. Compatibility with an MCP client does not establish an official partnership with that client.

Official sources: Higgs Overview. Checked September 28, 2026.

Account and connection requirements

Have an active paid Higgsfield subscription and an account in a supported client. In Claude’s connector settings, add a custom connector pointing to https://mcp.higgsfield.ai/mcp, then complete Higgsfield’s OAuth authorization. No Higgsfield API key is required for this connection.

Higgsfield’s instructions distinguish client routes: Claude uses the MCP connector; Cursor has a marketplace entry; its ChatGPT instructions use the official Higgsfield Plugin. The same guide routes Claude Code, OpenClaw and Hermes through its CLI. Do not assume those setup paths are interchangeable. Audio is specifically unavailable through the documented ChatGPT integration.

Official sources: Higgs Connect. Checked September 28, 2026.

Documented media workflows

Confirm the intended model, inputs and output type in the current tool options. A prompt mentioning an operation does not prove that your client exposes it.

Official sources: Higgs Overview · Higgs Connect. Checked September 28, 2026.

Standard credits apply

MCP generation spends existing account credits at standard rates. A website plan’s Unlimited or free-generation allowance does not make automated MCP requests free. The separate API product uses its own developer billing route; do not substitute API pricing for account-credit costs.

There is no single verified credit price for every media request. Check the model and workflow cost before approving generation, and re-check it before running repeated jobs.

Official sources: Higgs Overview. Checked September 28, 2026.

A controlled first workflow

  1. Choose the client-specific route in the official connection guide and authorize the intended account.
  2. Ask for your credit balance first; this checks account visibility without requesting a media generation.
  3. For a generation you choose to authorize, specify the media type, input asset, model and output requirements. Review any proposed repeated actions before they run.
  4. Check the result in Higgsfield Assets, review the output, and compare the remaining balance with the expected charge.

This is a suggested verification sequence, not a test performed by AI Tool Finder.

Official sources: Higgs Connect · Higgs Workflow. Checked September 28, 2026.

Limits and who should use it

Use this connection when media creation belongs inside an agent conversation. Use the web interface when you prefer direct controls or want to use eligible web-only benefits. Product developers needing a separate programmatic API should evaluate that product independently.

Your workflow depends on the third-party client, authorization state, account credits and currently exposed models. Review generated media for factual mistakes, visual defects and suitability before use. We have not connected an account, spent credits or measured reliability, generation quality or latency. Exact product launch date and the full live tool inventory are not established here.

Official sources

Checked September 28, 2026. Help-page dates are not treated as a product release date.