Cursor Sound MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playCompletionSoundD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool 'playCompletionSound' has a clear, distinct purpose that cannot be mistaken for any other tool.
With only one tool, naming consistency is inherently perfect. The tool name 'playCompletionSound' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is generally too few for most server purposes, as it provides minimal functionality and limits agent capabilities. For a sound-related server, one tool feels thin and under-scoped, lacking operations like stop, pause, or volume control.
The tool surface is severely incomplete for a sound server. With only a 'playCompletionSound' tool, there are obvious gaps such as stopping sounds, adjusting volume, listing available sounds, or playing different types of sounds, making it inadequate for typical sound management tasks.