Run Higgsfield MCP

Run Higgsfield MCP is a free agent skill maintained by Scopeful. It teaches an AI coding agent such as Claude Code, Cursor, Windsurf or Codex how to drive this tool correctly, so you do not have to re-explain it every session. Every published Scopeful skill is free and the install command is public, with no sign-in required. Install it with npx skills add higgsfield-ai/skills. Scopeful also tracks hand-verified USD pricing for 39 AI creative tools at https://www.scopeful.org/tools.

Connect any agent to the real Higgsfield MCP (HTTP at mcp.higgsfield.ai/mcp). Config snippets for Claude Code, Cursor, OpenCode, Codex, Windsurf, Gemini.

Tags: video, image, mcp, higgsfield, http

Install

npx skills add higgsfield-ai/skills

Reference

name: higgsfield-mcp description: Use this skill whenever the user wants to connect any agent (Claude Code, Cursor, OpenCode, Codex, Windsurf, Gemini) to the Higgsfield MCP server. Triggers include any mention of "Higgsfield MCP", mcp.higgsfield.ai, "add the higgsfield MCP to my editor", "Higgsfield MCP config", or asking an agent to register a remote MCP server. Do not trigger for the CLI install — that is the higgsfield-cli skill. Do not trigger for prompt structure, model selection, or Marketing Studio workflows — that is the higgsfield-mcp-better master skill.

Run the Higgsfield MCP

The real Higgsfield MCP is a remote HTTP server at https://mcp.higgsfield.ai/mcp. It is not an npx package. The cursor-plugin repo (higgsfield-ai/cursor-plugin/mcp.json) is the canonical config — verified 2026-06-30:

{
  "mcpServers": {
    "higgsfield": {
      "type": "http",
      "url": "https://mcp.higgsfield.ai/mcp",
    },
  },
}

The first connection opens a browser-based auth flow against the user's Higgsfield account. The token is stored by the agent and reused for subsequent calls. Sessions are short-lived; the MCP server returns 401 when the token expires and the user re-authenticates in the browser.

Verified facts (live 2026-06-30)

Assumed (not independently verified against a live session)

Install (per agent)

The config is the same for every host — only the file path changes. The mcpServers block from cursor-plugin/mcp.json is the canonical body.

Claude Code

Add to ~/.claude/mcp_servers.json (user-scope) or .mcp.json (project-scope):

{
  "mcpServers": {
    "higgsfield": {
      "type": "http",
      "url": "https://mcp.higgsfield.ai/mcp"
    }
  }
}

Reload Claude Code. The MCP appears in the tool list. First call opens the browser auth flow.

Cursor

Install via the Cursor Marketplace: search "Higgsfield" (/add-plugin -> Higgsfield), or copy the same JSON into ~/.cursor/mcp.json. Per the cursor-plugin README, the first connection prompts authentication.

OpenCode

Add to opencode.json at the project or user level:

{
  "mcp": {
    "higgsfield": {
      "type": "remote",
      "url": "https://mcp.higgsfield.ai/mcp"
    }
  }
}

Restart the OpenCode session. The MCP registers on connect.

Codex

Codex uses ~/.codex/mcp.json with the same mcpServers block. Restart after editing.

Windsurf / Gemini / others

Same JSON shape, different config-file path. The host-specific path is in each agent's docs; the mcpServers body does not change.

Verify

After saving the config and restarting the agent:

  1. List the registered MCPs. In Claude Code: /mcp. In Cursor: Settings -> Tools & MCPs. In OpenCode: opencode mcp list.
  2. The higgsfield entry should show a green / connected dot.
  3. Run a tiny test through the agent: "list the Higgsfield models". The agent should call whatever list / list_models / models tool the MCP exposes and return the catalog.
  4. If the dot is red, the most common causes are: (a) the agent cannot reach mcp.higgsfield.ai (corporate proxy / firewall), (b) the auth flow was canceled (re-trigger by removing and re-adding the server), (c) the JSON is malformed (validate with jq before restarting).

Live feedback (what the MCP gives back)

When NOT to use the MCP

Where to go next