
Fluxcut
io.github.Flux-AI-AgentPublished by GitHub account Flux-AI-Agentv1.46.0Updated Nov 7, 2026
Your agent makes a product video; you approve each step and publish. Needs a Fluxcut agent key.
Overview
Fluxcut lets an assistant make a short product video from a goal, driving each step while you approve and publish.
- What you can do
- Make a short product video from a stated goal, with the agent writing and filming the steps
- Drive the production step by step, pausing for your approval before publishing
- Use the bundled fluxcut-maker skill, which tells the agent how to make the video
- Run long waits of up to about four minutes where the client allows a five-minute tool timeout
- When to use it
- Useful when you want a coding agent to produce a promo or product video end to end, with a human approving each step before anything is published.
- Requirements
- Remote MCP endpoint at fluxcut.dev/mcp over streamable HTTP. A Fluxcut agent (maker) key, created in the Fluxcut settings, sent as an Authorization bearer header or via the FLUXCUT_KEY environment variable depending on the client. Optional wait parameter for longer tool calls. A second key is needed for a reviewer agent.
Installation
In SourceWeft
- Open Fluxcut in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Flux-AI-Agent%2Ffluxcut/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"fluxcut": {
"type": "http",
"url": "https://www.fluxcut.dev/mcp?wait=240",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
Fluxcut agent plugins
Fluxcut makes a short product video from a goal. These plugins let a coding agent make one for you: the agent writes, films and drives each step, and you approve each step and publish.
One install adds three things:
- the Fluxcut MCP server,
https://www.fluxcut.dev/mcp - the
fluxcut-makerskill, which tells the agent how to make the video - a five-minute tool timeout, so one wait can hold for four minutes instead of stopping at sixty seconds
Your key
Make a maker key at Settings → Agent keys. Then, in the terminal you start your agent from:
The Claude Code plugin keeps the key in your system's secure storage (the macOS Keychain, for example). The Codex and Cursor plugins store the name FLUXCUT_KEY, never the key, and read it from the environment, so for them add that line to your shell profile. fluxcut-capture, the filming tool the skill uses, reads FLUXCUT_KEY too.
Claude Code
The second line saves the key you exported into the plugin's settings. You can instead type it in Claude Code: /plugin configure fluxcut@fluxcut. The server loads once the key is set. The install command needs Claude Code 2.1.292 or later. On an older version, add the marketplace first: claude plugin marketplace add Flux-AI-Agent/fluxcut-plugin && claude plugin install fluxcut@fluxcut. Start a new session, then ask: "Use the fluxcut-maker skill to make a promo for ."
If you set Fluxcut up by hand before, claude mcp remove fluxcut so the plugin's server is the only one.
Codex
Codex reads FLUXCUT_KEY when it starts. Start a new task after installing.
Cursor
In Cursor, open the marketplace and install Fluxcut. Before it is listed there, clone this repo and copy cursor/ to ~/.cursor/plugins/local/fluxcut, then run Developer: Reload Window. Cursor reads FLUXCUT_KEY from the environment it starts in. Its waits use the server's default of 45 seconds.
Any other MCP client
Point it at https://www.fluxcut.dev/mcp with the header Authorization: Bearer <your key>. Add ?wait=240 only if the client allows tool calls of five minutes. fluxcut.dev/connect has the steps for each agent and the reviewer skill. A reviewer is a second agent with its own key.
What is in this repo
The skill is Fluxcut's published maker playbook. The minor version number is the playbook's version.
Privacy: https://www.fluxcut.dev/privacy · Terms: https://www.fluxcut.dev/terms · License: MIT
"Fluxcut" and the Fluxcut logo are trademarks of Fluxcut. The MIT License covers the files in this repo, not the name or the logo.
Source: README.md at commit ac96677
Tools
0Version history
3- v1.46.0LatestNov 7, 2026
- v1.44.0Nov 4, 2026
- v1.43.1Nov 3, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts