Skip to main content
Glama
Sign In
Otohiroi MCP

Otohiroi MCP

by koyomivanp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Otohiroi MCP

No user-submitted related servers found.

    Related Servers

    • strongerfx

      smartpage
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides local MCP tools to search and retrieve CC0 sound effects by keyword, category, duration, or ID, along with metadata, previews, and WAV/MP3 download URLs.
      MIT

    • Timbre MCP Server

      k33bz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • OtoMaker

      OtoMakerofficial

      og3-lab
      A
      license
      A
      quality
      C
      maintenance
      Lets 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.
      4
      MIT

    • Audio Studio MCP

      skycem
      A
      license
      Not graded
      quality
      C
      maintenance
      This 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.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation3/5

    Three tools (scan_game, find_replacements, open_sound_studio) all begin by detecting a game's oscillator sounds, and open_sound_studio's 'improve them' workflow is fuzzy about whether it also searches external libraries the way find_replacements does. suggest_search versus search_sounds is reasonably clear (query-building versus actual search), and get_sound/audition_sounds/fetch_sound form a clean pipeline. The scanning trio is the main source of potential misselection.

    Naming Consistency5/5

    All 11 names use snake_case with a verb-first pattern: find_replacements, list_packs, get_sound, search_sounds, audition_sounds, fetch_sound, add_pack, open_sound_studio, scan_game, suggest_search, find_elsewhere. No mixed conventions or vague bare verbs anywhere.

    Tool Count5/5

    Eleven tools sits squarely in the well-scoped range, and each covers a distinct step of the search-to-install workflow (query building, search, inspect, audition, fetch, pack management, in-game scanning). No tool looks like filler.

    Completeness4/5

    The surface covers discovery (search_sounds, suggest_search, find_elsewhere), inspection (get_sound), previewing (audition_sounds), installation with license recording (fetch_sound), plus pack and game scanning, which is solid lifecycle coverage. Gaps remain around pack/asset management: there is no remove_pack, no tool to list what has already been fetched into a project, and no way to inspect or clean up an existing project's non-oscillator audio.

    Resources