list-sound-effects
Lists the available sound effects.
LABSCO SUMMARY
A finished run announces itself instead of waiting to be noticed.
The whole surface is picking a cue and playing it, with list-sound-effects reporting what can be picked. What that buys is the difference between a run that finished and one that failed, audible from another window.
What it is
A two-tool server that plays a named sound effect and reports which ones are available.
What you get
- play-sound-effect plays a chosen cue — completion, new-type or error — and takes a message alongside it.
- list-sound-effects reports the sound effects available to play.
Requirements
Nothing to supply, beyond sound output on the machine running the server.
Setup effort
One command — npx -y sound-effects-mcp
USE CASES
01
Hearing that a long run finished while you are in another window
Check which cues exist, then have the agent play the completion cue when the task ends and the error cue when it does not.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
play-sound-effect
Plays a sound effect — completion, new-type or error — with an accompanying message.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"sound-effects-mcp": {
"command": "npx",
"args": [
"-y",
"sound-effects-mcp"
]
}
}
}npx
TERMINAL
npx -y sound-effects-mcp
