butterchurn-mcp
llms.txt1 starsChanged 31 days agoMITView on GitHub
FastMCP 3.4+ server: MilkDrop-style audio-reactive WebGL visualizer via butterchurn. Dual transport: stdio default, HTTP with MCP at /mcp. Full-screen Vite dashboard on 10879 proxies to API on 10878. Full detail: see llms-full.txt. Adjacency: backend/frontend paired per fleet WEBAPP_STANDARDS.
Files
# butterchurn-mcp > FastMCP 3.4+ server: MilkDrop-style audio-reactive WebGL visualizer via butterchurn. Dual transport: **stdio** default, **HTTP** with MCP at `/mcp`. Full-screen Vite dashboard on **10879** proxies to API on **10878**. **Full detail:** see `llms-full.txt`. ## Quick links - [README](README.md) — install, run - [glama.json](glama.json) — Glama discovery ## Ports (fleet range 10700–11500) | Role | Port | |------|------| | FastAPI + MCP HTTP | **10878** | | Vite dev (SPA) | **10879** | Adjacency: backend/frontend paired per fleet WEBAPP_STANDARDS.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms-full.txtllms.txt
- butterchurn-operatorSkill
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.

