OtoMaker
OfficialRelated Servers
Alternatives to OtoMaker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives Claude Code, Claude Desktop, Cursor and any other MCP client a local sound studio that turns plain-language requests into background music, instrument loops and sound effects, then re-styles, regenerates or extends them and exports seamless loops, fades and loudness-normalized WAV, OGG or FLAC files. Everything runs on Apple Silicon with no cloud service and no API key.604MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables MCP clients to generate background music, instrument loops, and sound effects from plain-language prompts, then edit them (variation, inpainting, extension) and finish them into seamless loops, fades, loudness-normalized WAV/OGG/FLAC files. All generation runs locally on your own machine without cloud services or API keys, with reproducible prompt/seed metadata saved alongside each output.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to turn structured creative briefs into repeatable, editable game music offline, producing compositions, sound settings, audio and MIDI exports, and validation checks through a local stdio MCP server.MIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic search of local audio samples by describing sounds, MIDI generation, stem separation, and other music production tools from Claude Desktop.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor and VS Code to synthesize speech locally in 31 languages, saving mp3, wav or ogg files, listing and installing catalog voices, and playing audio back through the system player — offline after the first run with no usage limits.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients such as Claude Desktop and Cursor to generate images and videos, synthesize speech, clone voices, and design custom voices from descriptive prompts. It supports stdio, REST, and SSE transport modes with configurable API hosts, keys, and local or URL-based resource output.493 npmMIT
TDQS
Scored across 4 tools
The four tools target clearly distinct stages: text-to-audio generation, model-based editing of existing audio, deterministic post-processing/export, and memory cleanup. Generate vs. edit could superficially overlap, but descriptions explicitly separate text-conditioned creation from audio-to-audio variation, inpainting, and continuation.
All tools follow a consistent snake_case verb_noun pattern: generate_audio, edit_audio, process_audio, unload_models. The only variation is the noun (audio vs. models), which accurately reflects the operation.
Four tools is well-scoped for an audio generation/editing/export server. Each tool maps to a necessary lifecycle stage, and there is no redundant surface area.
The surface covers the core lifecycle: generate audio, edit it, post-process/export it, and unload models. Minor gaps exist around explicit model loading/status or audio metadata inspection, but these are not essential given the returned WAV paths and automatic model reload behavior.