butterchurn-operator
Skill1 starsChanged 31 days agoMITView on GitHub
Operate the butterchurn-mcp visualizer backend (BPM sync, health, shutdown) and its Vite dashboard. Use when starting, probing, or driving the MilkDrop/WebGL visualizer for a DJ set or demo.
Files
Butterchurn Operator
Backend (FastAPI + MCP, default :10878)
- Health:
GET /api/health->{"status": "ok", ...} - Capabilities:
GET /api/capabilities(tool surface + versions) - MCP endpoint:
/mcp(streamable HTTP)
MCP tools
get_bpm(read-only): current beat driving the visualizer.set_bpm(bpm): 60..200. Called by mixx-dj-mcp during a DJ set.butterchurn_shutdown(confirmed=true): terminate the server (destructive).
Dashboard (Vite, default :10879)
Pages: Dashboard, Toolbox (engine picker), Presets, Visualizer (/visualizer?engine=shader&scene=gyroid-pulse), Tools, Settings, Logs, Help.
Launch
just serve (backend) + just web (frontend), or the fleet start.ps1.
Health-gate any scripted launch: poll /api/health until 200, then open the dashboard.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms-full.txtllms.txt
- llms.txtllms.txt
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.