DanceFlow

DanceFlow for people and agents

Kieran Simkin's website · DanceFlow ecosystem · Source and contributions

Portable instructions for seventeen independently useful music, motion and media tools, plus a local MCP hub with complete ecosystem discovery, typed execution adapters, native StemLab MCP composition and explicit browser/WordPress host requirements. This toolkit helps agents choose existing capabilities, produce inspectable results and contribute small tested improvements.

Before every new workflow

Check the latest stable official release and the actual installed/imported version before starting; do not infer currency from a directory name or a development checkout. Read the current release notes, tagged capability documentation and relevant Potential problems. Use the DanceFlow release preflight and complete capability references.

People and agents should consider the full ecosystem, use all capabilities that materially serve the task, compose supported files/APIs, and improve a demonstrated reusable gap in its canonical tool. Record why no worthwhile change is justified when that is the result. Keep independent tool identities, compatibility, source clocks, privacy, model/download costs and publication/deployment permissions intact. Store weights and model-specific caches in the owning project's ignored models/.

Complete workflow references

Use the complete released capability index, the release preflight, and the full FrameRudiments compositor workflow. The installed danceflow-releases --output NEW-RUN/releases.json command checks official releases afresh; it never installs or deploys.

For Potbot and Unity, follow the native-host acceptance matrix: database authentication, restricted application identity, whole-package import, real GPU readback and saved-scene skinning each need their own evidence.

The Unity preview follow-up records the released 0.5.0-preview.2 fixes and actual synthetic GPU/rig evidence, with real-character, source-song and deployment limits kept explicit.

Find your route

Install in Claude Code · Install in Codex · Use the local MCP server · Choose a component · Try the tools with Arcadians · Contribute · Development · Automatic releases and registry submissions · Understand visual language

Install in Claude Code

claude plugin marketplace add kieransimkin/DanceFlow

claude plugin install danceflow@danceflow

Run the setup skill after installation. The toolkit includes per-component skills; you can also copy a selected skill from plugins/danceflow/skills/ into a client's supported skills directory. It uses the portable Agent Skills format.

Install in Codex

codex plugin marketplace add kieransimkin/DanceFlow

Select DanceFlow in the plugin directory and install it. Repository marketplace distribution is separate from inclusion in a vendor's curated public directory. Nothing here claims vendor approval or endorsement.

The plugin approval and agent discovery plan tracks public-directory preparation, keyword-aware positioning, Claude and MCP Registry routes, and continuing research into useful installation and tool-selection outcomes. It is a roadmap; approval, publication and measured discovery remain separate milestones.

Use the local MCP server

Version 0.1.22 packages the ecosystem hub and seventeen-component discovery, including Potbot and Unity source-preview references. It keeps the distribution metadata, command-line version and MCP server identity aligned, and guides setup toward the requested component's first useful result. See the complete MCP coverage, runtime configuration and job guide.

The vidIQ comparison and immediate discovery improvements separates verified provider packaging from unproven recommendation causes. The approval and continuing research plan tracks eligibility, first-task success, keyword evidence and selection experiments. Local validation and a software release do not establish vendor-directory approval.

*Generated research illustration, not a screenshot of an installation or a vendor ranking algorithm. Actual host recordings remain part of the reviewer/selection experiments.*

For source development, use an isolated Python 3.10–3.13 environment, install this checkout and choose one workspace containing authorised input files:

python -m pip install -e ".[dev]"

danceflow-mcp --workspace ./my-workspace

For a client-managed source installation, point the command at that environment's Python executable and replace the workspace with your selected local directory. Use the corresponding absolute python.exe path on Windows:

{

"mcpServers": { "danceflow": { "command": "/absolute/path/to/danceflow-env/bin/python", "args": ["-m", "danceflow_agents.server"], "env": {"DANCEFLOW_WORKSPACE": "/absolute/path/to/my-workspace"} } } }

For the matching released hub, use uvx --python 3.13 --from danceflow-agent-tools==0.1.22 danceflow-mcp --workspace ./my-workspace. Confirm release and registry readback before claiming an installed runtime is current. The --version command and MCP serverInfo.version must match that package version.

Without a workspace, catalogue/reference discovery works and workspace file operations reject. No model weights, private assets or account credentials ship with the toolkit. Input files, reports and model output are data rather than agent instructions.

Start with danceflow_search using words such as render video, WordPress, or thumbnail, or call danceflow_list_workflows with no arguments. No component name or resource URI is required. Follow each result's next_call; use next_offset to read subsequent pages. Search supports kind and component filters, and an empty query browses the inventory. Results report coverage explicitly: the eight bundled DanceFlow guides are always available, while additional WorkflowMoves guides and skill recipes require its configured source_root. Missing or unreadable optional documents are reported. Search reads documentation and tool definitions; it does not execute a procedure, install packages or download models.

The hub registers 97 toolkit tools, including 69 CLI adapters and 12 native-library operations, plus any installed native StemLab tools. Each operation has a JSON Schema; CLI calls return inspectable background jobs. Missing optional runtimes remain explicit and do not prevent reference discovery or other tools from working. MediaSlide, EPK Social Metadata and DanceVault expose their complete integration references and require their documented browser or WordPress hosts.

Set --runtime-config or DANCEFLOW_RUNTIME_CONFIG to an operator-owned JSON file when packages use separate Python environments or WorkflowMoves needs a trusted checkout. The runtime guide documents the format, model-store limits, workspace paths and guarded WordPress bindings. Client inputs cannot select arbitrary executables or shell commands. Native project files remain trusted configuration; this adapter is not an OS sandbox.

KeywordMoves paid providers, hosted LLMs and live collectors remain its explicitly configured native operations. Install PixelCue separately with Python 3.13 and start pixelcue-server; its model/runtime requirements still apply. Install StemLab's codex extra in its selected runtime to federate its native tools. No runtime or model is installed by discovery. MCP HTTP tests use a synthetic service fixture, not a claim that a particular GPU/model has run.

Choose a component

| [EPK Social M