wubble_first_sound_effect — Wubble MCP Prompt
wubble_first_sound_effect
is one of 5 prompts on the
Wubble
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke wubble_first_sound_effect from your client
- Claude Code Wubble Prompt/wubble_first_sound_effect run in your project directory
- Claude Desktop Wubble Prompt/wubble_first_sound_effect ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wubble Prompt/wubble_first_sound_effect ~/.cursor/mcp.json
- VS Code Wubble Prompt/wubble_first_sound_effect .vscode/mcp.json
- Zed Wubble Prompt/wubble_first_sound_effect ~/.config/zed/settings.json
- Windsurf Wubble Prompt/wubble_first_sound_effect ~/.codeium/windsurf/mcp_config.json
- Cline Wubble Prompt/wubble_first_sound_effect ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wubble Prompt/wubble_first_sound_effect ~/.gemini/settings.json
- Grok Wubble Prompt/wubble_first_sound_effect .mcp.json (in your project root)
- ChatGPT Wubble Prompt/wubble_first_sound_effect Settings → Connectors → Advanced → Developer mode
- Claude.ai Wubble Prompt/wubble_first_sound_effect Settings → Connectors → Add custom connector
- LangChain Wubble Prompt/wubble_first_sound_effect pip install langchain-mcp-adapters
Other prompts on this server
Wubble also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.