Vibresia MCP
An official MCP server provided by Vibresia that allows AI agents to generate, compile, and preview GLSL-based music visualizations (vibes). It enables agents to write shader code, check for compilation errors, retrieve rendered images, and interact with audio uniforms to create dynamic visual experiences synchronized with music.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://vibresia.com/mcpWhat its tools do
8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Can change data (2)
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to vibresia.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Write GLSL music visualizations
- Check shader compilation status
- Retrieve rendered preview images
- Interact with audio uniforms
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- vibresia 1.0.0
- MCP protocol negotiated in check
- 2025-06-18
- Tools
- 8 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
8 advertised
create_vibescape — Create a vibescape
Use 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. The link draws and animates the vibescape in a browser, so it works for anybody who opens it, with or without the app. The vibescape is not in the public gallery until `share_vibescape` is called on it. Call `vibescape_reference` first for the uniforms and helpers the language has — a vibescape that ignores the music will look like a still image, and there is a linter that says so.
{
"type": "object",
"required": [
"code",
"name"
],
"properties": {
"code": {
"type": "string",
"description": "The vibescape: a GLSL function `vec3 render(vec2 p, float t)`. `p` is the position across the screen, centred on 0,0, and `t` is time in seconds. Return the colour as three numbers from 0 to 1. Read the music through the uniforms — uBass, uLevelSmooth, uBeatStrength, uScroll — or the picture will not move with the sound."
},
"name": {
"type": "string",
"description": "What to call it. A few words that say what the picture looks like."
},
"author": {
"type": "string",
"description": "Who to credit it to. Leave it empty and it is credited to Minith Labs."
}
}
}{
"title": "Create a vibescape",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}share_vibescape — Share a vibescape
Use this when a vibescape should be listed in the public gallery, where anybody can find it at vibresia.com/vibescapes. A vibescape is created unlisted; this is the separate act of putting it in front of people. The name and the author go with it, so make sure they are right before calling this.
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The share's id — the last part of the link, six characters. It is what `create_vibescape` returns."
}
}
}{
"title": "Share a vibescape",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}list_vibescapes — List the public vibescapes
Use this when somebody wants to see music visualisations other people have made, or wants something to look at before writing their own. Returns the public gallery: each vibescape's name, who made it, and a link that plays it.
{
"type": "object",
"properties": {}
}{
"title": "List the public vibescapes",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}get_vibescape — Get a vibescape's code
Use this to read somebody's vibescape, so it can be adapted or understood. Needs the id — the last part of the link.
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The share's id — the last part of the link."
}
}
}{
"title": "Get a vibescape's code",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}lint_vibescape — Check a vibescape
Use this after writing a vibescape, before sharing it. It reads the code and says what would make it look wrong — most often that it never reads the music, so the picture is the same in silence as at full volume. Cheap to call and it catches most of what goes wrong.
{
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "The vibescape's GLSL."
}
}
}{
"title": "Check a vibescape",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}vibescape_reference — The vibescape reference
Use this before writing a vibescape: it lists every uniform the music drives and every helper the language has, with what each is for. Writing a vibescape without it usually takes two attempts instead of one.
{
"type": "object",
"properties": {}
}{
"title": "The vibescape reference",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}get_palette — The palettes
Use this to find out how a vibescape's colours are graded. Vibresia puts every vibescape through one of five palettes, so bright colours come out muted unless the shader accounts for it.
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Which palette — NEON, EMBER, TOXIC, ABYSS or MONO. Leave it out to get all of them."
}
}
}{
"title": "The palettes",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}get_app — Get the Vibresia app
Use this when somebody wants the real thing: the app listens to the system audio directly, with no browser, and updates itself. It gives the download link and the one-line install command for macOS.
{
"type": "object",
"properties": {}
}{
"title": "Get the Vibresia app",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-02: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 200 ms
- 95th percentile latency
- 200 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 200 ms · metadata changed · 8 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http vibresia-mcp https://vibresia.com/mcpCodex
codex mcp add vibresia-mcp --url https://vibresia.com/mcpCursor
{
"mcpServers": {
"vibresia-mcp": {
"url": "https://vibresia.com/mcp"
}
}
}Cline
{
"mcpServers": {
"vibresia-mcp": {
"type": "streamableHttp",
"url": "https://vibresia.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"vibresia-mcp": {
"type": "http",
"url": "https://vibresia.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http vibresia-mcp https://vibresia.com/mcpClaude Desktop
{
"mcpServers": {
"vibresia-mcp": {
"url": "https://vibresia.com/mcp"
}
}
}Windsurf
{
"mcpServers": {
"vibresia-mcp": {
"serverUrl": "https://vibresia.com/mcp"
}
}
}Let your agent find its tools
Find servers like Vibresia MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other ai and machine learning servers
Do you run Vibresia MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.