FLUX MCP server generate_video: what Sume's hosted MCP has
BFL's FLUX MCP server gained generate_video and enhance_video on 2026-08-11. Sume's hosted MCP has its own generate_video and video_upscale_create tools.
BFL's FLUX MCP server added generate_video and enhance_video tools on 2026-08-11, and those run BFL's models. Sume's hosted MCP has its own generate_video tool, which routes to sume/auto unless you name a catalog model, plus video_upscale_create; it has no tool called enhance_video.
Sume's side is from its MCP overview and tools and gates pages, BFL's from its release notes, read 2026-09-29.
Which video tools does each server list?
The names match in one place and differ in the rest, so an agent prompt that says enhance_video will not find a tool of that name on Sume.
| Job | BFL FLUX MCP server | Sume hosted MCP |
|---|---|---|
| Make a clip | generate_video | generate_video |
| Improve a draft | enhance_video | no tool of that name |
| Upscale a clip | not named in the release note | video_upscale_create |
How do I connect Sume's server?
Add the remote HTTP endpoint and sign in. Interactive clients should prefer OAuth over pasting an API key.
claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sumeWhat gates a paid generate_video call?
Paid tools need an idempotency_key, and dry_run=true returns an admission and cost preview without submitting. After a real submit, poll with jobs_status or jobs_wait and read jobs_result. Wallet admission is the spend gate.
Which model does the tool use?
Omit payload.model and the call routes to sume/auto. To pin a model, name a catalog id from video-router_models.
What if my agent needs an enhance step?
BFL's list ties enhance to its FLUX 3 Video draft enhance mode. Nothing on Sume's tool list is named for it. The closest Sume tool for improving an existing clip is video_upscale_create, which upscales rather than re-directs, so it is a different operation, not a stand-in. For a redo, submit a new generate_video call with a changed prompt.
How does a client discover the live tool list?
Ask the server. Discovery tools such as catalog_list, tools_list and tools_schema tell the client which tools exist in the current session, and the docs note hosted MCP is not full parity with the HTTP API. Tool names in a blog post can drift, so have the agent call tools_list before it writes a plan around one.
Can one client connect to both servers?
MCP clients can hold several remote servers at once, so a client can list BFL's server and Sume's side by side. The practical problem is naming: both list a tool called generate_video, and an agent may pick the wrong one from an ambiguous request. Say which server you mean in the prompt, or check the tool descriptions each server returns before the agent chooses.
Keep the spend gates in mind too. Sume's paid tools ask for an idempotency_key, and you should read what BFL's server asks for on its own page before you let an agent call it unattended.
Sources
Related posts
More in Developers
- 413 payload_too_large on a Sume Format run: the 4 MiB body cap
A Format run body over 4 MiB answers 413 payload_too_large. Shrink input, send media by URL, and tell it from attachment_too_large and a null payload.
- Cap what one Format run can spend with generation_spend_cap_usd
Every Sume Format run has a generation spend cap. Send generation_spend_cap_usd to set it: up to 500, null runs at 500, 0 is rejected. What happens at the cap.
- Video judder with mixed frame rates: Timeline's warning
Judder on a joined video comes from resampled frame rates. Sume's Timeline warns output_fps_resamples_sources when a source rate differs. How to read it.
- Gemini 3.8 Flash function calling: let it start a Sume video job
Declare a function for Gemini 3.8 Flash, run it against Sume's /v1/videos when the model returns a functionCall, and reply with a functionResponse with job id.
Written by Sume