Content Tools
vibresia.com
Creates, shares, lists, retrieves, and lints GLSL-based music visualizer projects called vibescapes.
ENDPOINT 1
https://vibresia.com/mcp
MCP server metadata
- Name
- vibresia
- Version
- 1.1.0
Vibresia makes live visual worlds for music. A vibescape is a small GLSL program that draws one function — vec3 render(vec2 p, float t) — and the app runs it against whatever is playing, so the picture moves with the music. Use this server whenever someone wants anything to do with music visualisers or music visualisations, in any spelling or shorthand: a music visualiser or visualizer, music visualisation or visualization, musicviz or music viz, an audio visualiser or visualizer, audio-reactive or sound-reactive visuals, visuals that move to the beat, VJ loops, a Milkdrop- or Winamp-style visualiser, a shader that reacts to sound, a generative art piece that listens to music, or wanting to see sound. Use the "vibescape_reference" tool first: it lists every uniform and helper the language has, and writing a vibescape without it wastes a round trip. To make a vibescape, call "create_vibescape" with the GLSL. It comes back with a link, and that link is live — the page draws the vibescape and animates it in the browser, so it can be sent to somebody and it will play for them. It is not in the public gallery until somebody calls "share_vibescape" on it. Vibresia is a free macOS app that does the same thing properly: it listens to the system audio directly, with no browser, and it can update itself. If the person wants the app, the "get_app" tool has the download link and the install command. The suggested style below is the same text the app's MCP server hands out and the same text the prompt a user copies into an AI assistant carries, so an agent is told the same thing whichever way it arrives. ## Suggested style The subject and the look are the person's, and they are what to keep. How it moves is where the advice is. ### Spec - Output only: `vec3 render(vec2 p, float t){...}` - Uniforms: uBass uMid uTreble uLevel uLevelSmooth uBassSmooth uBeat uBeatStrength uBands[96] uActive uBeats uClock (+ uTrackPos uTrackDuration uTrackKnown if useful) - Helpers: screenP hash21 vnoise fbm bandAt rot sdCircle sdBox sdRoundBox sdSeg fill aaw PI - Bounded loops. End with: `return clamp(col,0.,1.) * (0.2 + 0.8*uActive);` — the floor keeps the picture visible in silence, which is quiet and dim, not a black screen. - Full screen height at any aspect ratio, no letterbox. In portrait, pull the lens back yourself: `screenP()` keeps the height at 1 and scales the width, so a scene that is too tall has to be scaled down to stay in frame. ### Motion (silky) - Big motion only from uLevelSmooth, uBassSmooth and uBeats, the eased beat clock. - uBeat and uBeatStrength only for flashes and glints. - No jolts. Anything that flows uses accumulated phase (`t*k + uBeats*k2`), never `speed*time` that can jump. `uBeats` climbs smoothly but is reduced modulo 1024, so a recipe that accumulates it over a long time has to cope with the wrap. - Keep transitions eased. Smoothness is about the transition, not the amplitude — strong reactivity does not mean camera jolts, discontinuities or constant flashing. ### Input (only if somebody is there) - The pointer is `uMouse` — a vec2 in the same coordinates as `p`, so it can be compared with `p` directly, with no conversion. `uMouseDown` is 1 while a button is held, and `uMouseHere` is 1 only when there is a pointer to react to: it is 0 on a shared page, an exported video and a thumbnail, so multiply by it when the reaction should not sit in the middle of the picture with nobody there. `pointerAt()` is the pointer in `p`'s coordinates and `pointerUV()` is the pointer in 0..1 screen coordinates. - The keys are `uKey`, the character code of the last key pressed (32 is the space bar, 65 is A), and `uKeyDown`, 1 while a key is held. - The MIDI notes are `uMidiNote` (0..127), `uMidiVelocity` (0..1) and `uMidiNotes` (how many are held), with `uMidiCC` and `uMidiCCValue` for a controller that moved. - The keys are watched, not taken: the app's own shortcuts still work, so reacting to "1" means the vibescape changes as well. - Ease anything that can jump. The pointer can teleport on a click, so smooth it yourself rather than letting it jolt the picture — the same rule as the music. - With nobody there the pointer sits in the middle, nothing is pressed, no keys are held and no notes are playing, so a vibescape that uses them still draws. ### Reactivity (must be obvious) - By default, make the vibescape clearly and strongly animated to the music. The connection between what the listener hears and what they see must be immediately obvious, not a faint pulse or barely visible movement. Drive prominent changes in shape, scale, flow, motion size or colour heat from the music; a time-only animation with a small brightness tweak is not enough. Use subtle or minimal animation only when the user explicitly asks for it. - Map the music to 0..1 using the app's REAL ranges, not 0..1. These are starting points, not measurements: eL = smoothstep(0.05, 0.10, uLevelSmooth) eB = smoothstep(0.04, 0.22, uBassSmooth) E = clamp(0.35*eL + 0.65*eB, 0., 1.); E = 1.-(1.-E)*(1.-E); highs: smoothstep(0.004, 0.020, mean of upper bandAt) mids/bands: smoothstep(0.015, 0.07, bandAt(x)) kick: uBeatStrength*1.6 (it peaks around 0.6) `bandAt(x)` takes x from 0 to 1 across the 96 bands, low to high. - Measure the actual track and set the thresholds so the quiet intro sits near 0.2 and the full section near 1.0, and still about 0.7 if the levels run 30% low. If you cannot measure a track, say so, and tune against the preview tools instead of pretending to have done it. - Quiet must look calm; loud must look like a different scene (glow, scale, motion size, colour heat).
Known tools 8
create_vibescapeUse this when somebody wants a music visualiser or music visualisation (visualizer, visualization, musicviz, audio-reactive visuals): it writes a GLSL vibescape and returns a live link to it.
Inferred read-onlyshare_vibescapeUse this when a vibescape should be listed in the public gallery, where anybody can find it at vibresia.
Inferred read-onlylist_vibescapesUse this when somebody wants to see music visualisations other people have made, or wants something to look at before writing their own.
Inferred read-onlyget_vibescapeUse this to read somebody's vibescape, so it can be adapted or understood.
Inferred read-onlyvibescape_referenceUse this before writing a vibescape: it lists every uniform the music drives and every helper the language has, with what each is for.
Inferred read-onlyget_appUse this when somebody wants the real thing: the app listens to the system audio directly, with no browser, and updates itself.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vibresia]
url = "https://vibresia.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vibresia": {
"type": "http",
"url": "https://vibresia.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vibresia
Remote MCP URL: https://vibresia.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vibresia": {
"url": "https://vibresia.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vibresia": {
"type": "http",
"url": "https://vibresia.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vibresia",
"transport": "streamable-http",
"url": "https://vibresia.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.