MCP connector
HFLUX provides a remote connector that follows the standard MCP specification. Copy the server address from your account screen, register it in Claude or Codex, and you can request image and video generation from the chat window. Connections have been verified in Claude and Codex.
Credits are deducted on the same basis as on the web.
Connecting from Claude
- In Claude, go to Customize then Connectors
- Press ＋, choose Add custom connector, and paste the MCP server address copied from your HFLUX account screen
- Press Add and approve on the authorisation screen that opens
The Claude free plan allows one connector.
Connecting from Codex
- Open a terminal and run the
codex mcp add hflux --url …command shown on your account screen - Approve on the browser authorisation screen that opens automatically
- Check that
hfluxappears in the MCP server list in your Codex settings
The thirteen tools
| Group | Tools |
|---|---|
| Look around | hflux_list_models · hflux_get_credits · hflux_estimate_credits |
| Create | hflux_write_prompt · hflux_prompt101 · hflux_generate_image · hflux_submit_video · hflux_generate_audio |
| Check | hflux_get_job · hflux_list_jobs |
| FLOW | hflux_flow_plan · hflux_flow_start · hflux_flow_get |
Call hflux_estimate_credits before generating and the chat can tell you what a request will cost before it runs.
Credit caps
Per-user caps exist so that an agent stuck in a loop is stopped before it reaches your balance.
| Limit | Value |
|---|---|
| Single call | 1,500 credits |
| Hourly total | 20,000 credits |
| Generation tool calls | 20 per minute |
| Read tool calls | 60 per minute |
Reads and generations are counted in separate buckets, so polling a job status does not eat into your generation allowance. In every case the server blocks once your balance is reached, so you cannot lose more than you hold.
Authentication and revoking
Only tokens issued through OAuth are accepted. HFLUX does not use the token passthrough pattern that the MCP specification forbids, and validates only tokens valid for HFLUX resources; a browser login session token will not get through.
Connected apps can be revoked at any time from the connected apps list on your account screen. Once revoked, that app can no longer spend your credits.
Frequently asked questions
Can I use HFLUX directly from Claude or Codex?
Yes. HFLUX provides a remote MCP connector. Copy the server address from your account screen, register it in Claude or Codex, and you can request image and video generation from the chat window. It follows the standard MCP specification and connections have been verified in Claude and Codex. Credits are deducted on the same basis as on the web.
How do I connect it to Claude?
In Claude go to Customize then Connectors, press the plus button, choose Add custom connector, and paste the MCP server address copied from your HFLUX account screen. Press Add and approve on the authorisation screen that opens. The Claude free plan allows one connector.
How do I connect it to Codex?
Open a terminal and run the codex mcp add command shown on your HFLUX account screen. Approve on the browser authorisation screen that opens automatically, then check that hflux appears in the MCP server list in your Codex settings.
Which tools are available?
Thirteen tools: list models, get credit balance, estimate credits, write a prompt, Prompt 101, generate an image, submit a video, generate audio, get a job, list jobs, and plan, start and get a FLOW.
Can a looping agent burn through my credits?
Per-user caps are in place. A single call cannot exceed 1,500 credits and the hourly total is capped at 20,000. Generation tools are limited to 20 calls per minute and read tools to 60, counted in separate buckets. In every case the server blocks once your balance is reached, so you cannot lose more than you hold.
Can I revoke the connection?
Yes, from the connected apps list on your account screen at any time. Once revoked, that app can no longer spend your credits.
How does authentication work?
Only tokens issued through OAuth are accepted. HFLUX does not use the token passthrough pattern that the MCP specification forbids, and validates only tokens valid for HFLUX resources. A browser login session token will not get through.