SFX Brew
Related Servers
Alternatives to SFX Brew
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables coding agents to synthesize and play video-game sound effects by translating natural-language descriptions into layered synthesis specs, then rendering normalized WAV files.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, rank, and retrieve 330 synthesized sound effects, themes, and spoken lines, and to generate ready-to-paste playback code or whole-app sound kits through a zero-dependency stdio MCP interface.227 npmMIT
- AlicenseAqualityCmaintenanceGenerates four game-ready AI sound effect candidates from a text description, lets users audition them, and installs only the selected WAV into Unity, Godot, or generic game projects.628 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables local generation of game sound effects from text prompts using Stability AI's Stable Audio Open model, with no API keys or per-generation cost.1MIT
- AlicenseAqualityDmaintenanceA game-agnostic MCP toolkit for composing chiptune/retro MIDI and rendering game audio, enabling AI agents to generate multi-track MIDI files and render them to OGG/WAV.7MIT
- AlicenseAqualityCmaintenanceLets MCP clients such as Claude Code, Claude Desktop and Cursor generate background music, instrument loops and sound effects locally on Windows from plain-language prompts. It also edits and processes the results — variations, inpainting, extension, trimming, loudness normalization, seamless looping and WAV/OGG/FLAC export for game engines and video editors.4MIT
TDQS
Scored across 4 tools
Each tool has a clear role in the pipeline: discover presets, synthesize from a preset, render a hand-edited patch, and export browser JS. The only mild overlap is that generate_sfx and render_patch both output WAV files, but their inputs (preset vs. patch JSON) and intended stages are clearly distinguished.
All four names follow a clean verb_noun snake_case pattern: list_presets, generate_sfx, render_patch, get_js_code. The convention is predictable and readable.
Four tools is compact and well-scoped for a procedural SFX generator, and each tool earns its place in a coherent discover → generate → fine-tune → export workflow. Nothing feels redundant or missing at the count level.
The core lifecycle is covered: browsing presets, generating variants with seeds, editing patch JSON for fine-tuning, and exporting playable JS snippets. Minor gaps remain, such as no audio preview/playback tool and no way to list, manage, or delete previously generated files.