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 |
|---|---|
| playCompletionSoundC | Plays a completion sound when called |
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 confusion or overlap between tools. The single tool has a clear, distinct purpose that cannot be mistaken for another.
A single tool inherently has perfect naming consistency, as there are no other names to compare it against. The tool name 'playCompletionSound' follows a clear verb_noun pattern.
One tool is too few for a server's purpose, as it severely limits functionality and suggests the server is trivial or incomplete. A single sound-playing tool does not justify a full MCP server.
The server is severely incomplete, as it only offers a single sound-playing tool with no other related operations (e.g., stop sound, list sounds, adjust volume). This minimal surface fails to cover any meaningful domain.