Home / MCP registry index / com.gomosounds/gomo-sounds

Gomo Sounds

com.gomosounds/gomo-sounds in the official MCP registry. Endpoint https://gomosounds.com/mcp.

The registry describes it as: Game audio by chat: plan, generate and pick sound effects, music and voice lines.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http gomo-sounds https://gomosounds.com/mcp

{
  "mcpServers": {
    "gomo-sounds": {
      "url": "https://gomosounds.com/mcp"
    }
  }
}

code --add-mcp '{"name":"gomo-sounds","type":"http","url":"https://gomosounds.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_game game_progress sounds_for_folder find_sounds get_entity list_games get_game generate_sounds generate_music derive_music create_tracks job_status list_voices create_voice generate_voice choose_sound share_sound create_entity create_event delete_sound list_folders set_sound_direction create_folder move_entities set_game_visibility save_sound export_game get_manifest sync_scenes mark_installed godot_plugin game_scenes place_scenes suggest_game_setup accept_terms approve_spending gomo_guide

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-12): 53d8768aa0354f8e. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-gomosounds-gomo-sounds/badge.svg)](https://lazaretto.dev/mcp-registry/com-gomosounds-gomo-sounds)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Music and podcasts MCP servers