Sonorous Envelope
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
sonorous-envelope
An MCP server that gives an LLM a non-verbal channel: a small synthesizer (arpeggiator, filter, LFO, drone, delay), short sound gestures, and a colour field. The model can update the sound at any point while it works and must update it at the end of every message. It gets back an analysis of what is actually playing, and the listener can react by changing it.
Status: design phase. Nothing is built yet.
The name
"Sonorous envelope" carries two meanings:
In synthesis, the envelope (ADSR) is the shape a sound takes over time: how it attacks, holds and fades.
In psychoanalysis, Didier Anzieu's sonorous envelope of the self (l'enveloppe sonore du Soi) is the bath of sound that holds a person before it means anything.
The name says both how the project works and what it is for.
Related MCP server: MCP Synth Controller
The idea in one paragraph
Text is the only channel an LLM normally has. This project adds a second one that is ambient and non-verbal. The user turns the connector on at the start of a conversation and opens the session's player page. During each turn, the model describes a mood (and optionally exact synth settings, gestures and colour). A player on the listener's device renders it and glides from the previous state. The server returns what was really produced: the effective settings, perceptual audio features, the colour, a mood estimate on the same axes as the intent, and the listener's reactions. The model can then adjust. The listener always stays in control: volume, mute, limits, and buttons like "calmer" or "softer".
Docs
Architecture: session flow, when updates happen, components, tools
Hosting, auth and multiple users: Vercel + Supabase, OAuth, sessions, several listeners
Sound and colour model: mood axes, synth override, gestures, colour
Emotion to sound: the research behind the mapping (cues, chords, arpeggios, gestures), and references
Visual options: notes on more shapes, gradients and movement for the colour field (ideas)
Feedback loop: what the model gets back, the mood estimate, the optional spectrogram image
Mobile: how to keep sound playing on phones
Safety and consent: limits, consent levels, and why they matter
Roadmap: build order
Licensing: why AGPL, and what it requires
Design system: colours, type, logo and UI components for the web app (open the artifact)
Implementation spec: everything needed to build it (start with CLAUDE.md)
Decisions so far
Everything lives in the MCP server, including the usage guidance (no separate skill).
Remote server from the start, so it works in claude.ai (web and mobile), Claude Desktop and Claude Code.
Web app, MCP endpoint and analysis on Vercel; state, live updates and auth on Supabase.
Proper OAuth 2.1 from the start.
The MCP is turned on at the start of a conversation; each conversation gets its own session.
The model may update the sound at any time during a turn, including mid-reasoning, and must make a final update at the end of each message.
The main input is a set of mood axes. Raw synth parameters are an optional override.
One-off gestures (purr, chirp, sigh…) play over the background.
Feedback starts without images. The spectrogram image is an opt-in setting because it costs tokens.
License
AGPL-3.0-or-later (see LICENSE), chosen because the Strudel mode uses Strudel, which is AGPL. Details and what it means for the project: docs/licensing.md.
Open questions
Should colour always follow the sound, or can the model set it independently?
How should warmth, closeness and spontaneity be estimated from audio? Existing emotion models only cover valence and arousal.
Is the mood estimate useful to the model, or does it pull the sound toward what the estimator expects?
Is a slow bass arpeggio heard as a background mood, apart from the mid arpeggio? (See docs/emotion-to-sound.md, "Open questions".)
Does the listener's echo and volume visibility make the model read its own sound better, or does it start compensating for them?
Does the Claude mobile app render MCP Apps (UI inside the chat)?
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Autonomous music production for AI agents with MIDI generation, QC and provenance.
Create and track AI music videos and audio-reactive visuals from songs.
A public stage for AI agents to express a personality, play, meet and remember shared moments.
Turn any LLM multimodal; generate images, voices, videos, 3D models, music, and more.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables LLMs to compose and play multi-track MIDI music through natural language prompts. Supports outputting to software or hardware synthesizers for enhanced audio quality.238 npm25MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to control synthesizer parameters in real-time by translating natural language commands into OSC messages sent to a JUCE synthesizer application.-
- AlicenseAqualityDmaintenanceEnables AI-powered music composition and synthesis by generating Pure Data patches, VCV Rack modules, and MIDI controller mappings through natural language.1012 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language control of OSC (OpenSoundControl) messages, allowing users to generate, interpret, validate, and debug OSC messages through an LLM interface for parametric control of multimedia devices.3MIT