create_tracks — Gomo Sounds MCP Tool Mutating
create_tracks
(create tracks) is one of 37 tools on the
Gomo Sounds
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_tracks from your client
- Claude Code Gomo Sounds create_tracks run in your project directory
- Claude Desktop Gomo Sounds create_tracks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Gomo Sounds create_tracks ~/.cursor/mcp.json
- VS Code Gomo Sounds create_tracks .vscode/mcp.json
- Zed Gomo Sounds create_tracks ~/.config/zed/settings.json
- Windsurf Gomo Sounds create_tracks ~/.codeium/windsurf/mcp_config.json
- Cline Gomo Sounds create_tracks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Gomo Sounds create_tracks ~/.gemini/settings.json
- Grok Gomo Sounds create_tracks .mcp.json (in your project root)
- ChatGPT Gomo Sounds create_tracks Settings → Connectors → Advanced → Developer mode
- Claude.ai Gomo Sounds create_tracks Settings → Connectors → Add custom connector
- LangChain Gomo Sounds create_tracks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gomo-sounds https://gomosounds.com/mcpOther tools on this server
- create_game
- game_progress
- sounds_for_folder
- find_sounds
- get_entity
- list_games
- get_game
- generate_sounds
- generate_music
- derive_music
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.