mark_installed — Gomo Sounds MCP Tool
mark_installed
(mark installed) 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 mark_installed from your client
- Claude Code Gomo Sounds mark_installed run in your project directory
- Claude Desktop Gomo Sounds mark_installed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Gomo Sounds mark_installed ~/.cursor/mcp.json
- VS Code Gomo Sounds mark_installed .vscode/mcp.json
- Zed Gomo Sounds mark_installed ~/.config/zed/settings.json
- Windsurf Gomo Sounds mark_installed ~/.codeium/windsurf/mcp_config.json
- Cline Gomo Sounds mark_installed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Gomo Sounds mark_installed ~/.gemini/settings.json
- Grok Gomo Sounds mark_installed .mcp.json (in your project root)
- ChatGPT Gomo Sounds mark_installed Settings → Connectors → Advanced → Developer mode
- Claude.ai Gomo Sounds mark_installed Settings → Connectors → Add custom connector
- LangChain Gomo Sounds mark_installed pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gomo-sounds https://gomosounds.com/mcp
Other 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
- 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
- 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.