Released Apr 2025

Record sheet · No. 026
vibe-mcp
An MCP server that reads the code you are working on and generates music to match — the genre comes from the programming language, and the mood partly from the code’s binary representation.
GitHub avatar of trevhud, not the project’s own logo — taken from github.com on 2026-10-01.

What it is
An MCP server that turns the code in front of you into music, generating a matching track from the snippet it is handed and crossfading between pieces so the music never stops.
It exposes three tools (start a session, generate more as the current track runs out, stop) analyses the code snippet it is handed, and asks a music-generation API for a track matching what it found. Playback happens on the server, not in the editor, with a two-second crossfade between tracks so the music does not stop while the next piece is being generated.
Who built it
A Seattle-based AI consultant who describes his work as helping clients automate with AI and lists Vaib Studio, an AI consultancy, as his company; its portfolio includes a Cline product-leadership case study. He has been on GitHub since 2012 and has fifty-seven public repositories, a large share of them forks of other people’s work.
Build log
6 stages- 01
Three tools, and playback on the wrong side of the wire
The server exposes
start_vibe_session,generate_more_musicandstop_vibe_session, all of which take the current coding context as a required argument. The unusual choice is where the music comes out: playback runs on the MCP server itself, through thespeakerpackage; the audio never goes back to the editor. That is what makes the crossfade possible —playback.tsholds two player slots and fades one out over two seconds in fifty-millisecond steps while the other fades in, so asking for the next track early is seamless, with no gap. FFmpeg is a hard requirement, pulled in throughfluent-ffmpeg, and the README lists an install command for each of the three platforms. - 02
How code becomes a music prompt
buildPrompt()truncates the snippet to 1,200 characters and derives the musical parameters from it with keyword heuristics, then pastes the raw code into the prompt under aCODE CONTEXT:heading. Genre comes from the detected language, and the table is the most legible thing in the repository: JavaScript is lo-fi house, chillhop and trip hop; TypeScript is synthwave and ambient techno; Python is ambient and downtempo; Java is orchestral and cinematic; Ruby is jazz and bossa nova; Go is minimal techno; Rust is industrial and dark ambient; PHP is vaporwave and future funk; SQL is acid jazz and broken beat; and shell scripts are breakbeat, drum and bass and jungle. Language detection is fourteen regular expressions, tempered by the file extension. Tempo comes from ananalyzeComplexity()score bucketed into five ranges (60–80 BPM for the simplest code up to 140–160 for the most complex) and then a random offset is added inside the chosen range. - 03
The mood is read out of the binary
The best detail is
analyzeCodeBinaryForMood(), which converts the source to a string of bits and reads moods off that. The ratio of ones to zeros above 0.6 yields “dense” and “intense”, below 0.4 yields “sparse” and “minimal”, and anything between yields “balanced”. It then counts occurrences of the literal bit pattern0101and adds “rhythmic” and “patterned” if it appears more often than a threshold the source itself annotates as// Arbitrary threshold. Finally it walks the bits in chunks to measure how fast the density of ones changes, under a heading the author put in scare quotes: a “Differential Equation” simulation. The function’s own docblock describes it as a conceptual example. - 04
The instruction file left in the repository
The repository carries a
.clinerules/directory (the per-project instruction file Cline reads) containing a single short document calledNo test.md. In full: “Please don’t test without me asking you to. Do not run the application. Always use the MCP instead. NEVER RUN node dist/index.js!!!!!” It is four lines of the author telling his coding agent what not to do, and it is the most direct evidence in the repository of how the project was built. The rule is also slightly out of step with the build script, which emits tobuild/, notdist/. - 05
What the numbers look like
Nine commits across five days, from 27 April to 2 May 2025, and nothing since. One author, no releases, no tags, and no issues or pull requests ever opened. Twelve stars and four forks. The README ends with a
## Licenseheading and the single word “MIT”, but the repository contains no licence file, so GitHub reports no licence for it. Thepackage.jsonmarks the packageprivate, pins the MCP SDK at0.7.0, an exact pre-1.0 version, and listsspeakerandfluent-ffmpegalongsideaxiosanddotenv. Running it needs at least one paid key, from Stability AI or PiAPI, and the generator chosen depends on which one you have. - 06
The homepage field points somewhere else
The repository’s homepage field is set to
cline.bot, the site of the editor the server plugs into; the field names nothing of the project’s own. Along with theclineandmcptopics and the.clinerulesdirectory, it places the project squarely inside the Cline ecosystem. There is no separate demo, and the last commit added thelanguageparameter to the tool schemas, which lets the model report the language; otherwise it has to be guessed from the code.
Adjacent records
All records →No. 142
DSCODE
A macOS terminal coding agent built on DeepSeek Harness, carrying its own pinned harness profile, a terminal package it patches at build time, and a session layer: sessions that message each other, Ultra sub-agents, reviewed approvals, scheduled runs.
No. 140
Agents Universe
An open-source agent platform that keeps one project context shared by everyone working in it. Agents read the whole knowledge base when a project is opened and write what they learn back into the same files while they work; knowledge is Markdown on disk with a database index behind it, and there is no embedding model or vector search.
No. 139
anything2explainer
A skill for Claude Code and Codex that turns a topic, or a document, into a 1280×720 narrated explainer film, with every frame drawn in code rather than generated and each agent in the parallel build writing one Remotion component. The same author’s video-shotcraft makes product promos out of 157 shot cards and a sound-design pass; this one is driven by the narration, ships no sound effects or music, and freezes the words into frame numbers before any shot is built.


