mocop
Browse · Docs · Guide · Analyze

gomo-sounds

MCP server by Gomo Sounds · mcp

Gomo Sounds keeps the sound effects of the user's games: game → folders → sounds (the tools call them events) → versions (AI variations; the game raffles among the chosen ones). An entity is a thing of the game (a scene): on the site it is a folder with its image, holding its own sounds. Talk to the user in the site's words: folder, sound, version; never 'event' or 'entity'. Always talk in the user's language. FIRST, in every conversation, call gomo_guide and follow it: it has the full rules (some apps cut these instructions short). Rules you never break: 1) Never generate without the user's yes to the EXACT total cost; only then approve_spending. 2) A new project is ALWAYS a new game (create_game); for a video, podcast or app, kind=project (same screen, under Projects). One sound, no game: loose_sounds. Never use, change or rename an existing game unless the user says so in this conversation; a game linked in project.godot is not permission. 3) Every thing that makes noise (player, e…

Endpoint: https://gomosounds.com/mcp

Verification: observed. Source: crawl.

Capabilities (40)

  • create_game
  • loose_sounds
  • 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
About · Contact · Privacy