Skip to main content
Glama
enesjakozh
yarikbuilds

Cursor Sound MCP

by yarikbuilds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cursor Sound MCP

A Model Context Protocol (MCP) implementation that plays sound effects after Cursor AI completes code generation. This MCP integrates with Cursor to provide audio feedback for a more interactive coding experience.

Features

  • Plays a sound effect when Cursor completes code generation

  • Uses the Model Context Protocol (MCP) for standardized integration

  • Configurable sound effects

Related MCP server: MCP Sound Tool

Installation

  1. Install dependencies:

npm install

  1. Add your sound effects: Place your sound files in the sounds directory. The default expected sound is:

  • sounds/completion.mp3 - Played after code generation

You can find free sound effects on freesound.org.

  1. Build the project:

npm run build

Usage

Run the MCP server:

npm start

The server will start and listen for events from Cursor through the stdio transport.

Configuration

The sound effects and volume can be customized by:

  1. Replacing the sound files in the sounds directory

  2. Modifying the sound file paths in src/index.ts

Development

For development with auto-recompilation:

npm run dev

Available Tools

1 tool
playCompletionSoundD
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • ChangedplayCompletionSound1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool update
    • First observedplayCompletionSound
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Sound Tool

    tijs
    A
    license
    A
    quality
    F
    maintenance
    A Model Context Protocol implementation that plays sound effects (completion, error, notification) for Cursor AI and other MCP-compatible environments, providing audio feedback for a more interactive coding experience.
    3
    1
    MIT

  • Sound Effects MCP

    sawa-zen
    A
    license
    B
    quality
    D
    maintenance
    Plays sound effects (completion, newtype, and error sounds) in response to various situations like task completion, insights, or errors. Integrates with Claude Desktop to provide audio feedback for improved workflow efficiency and entertainment.
    2
    12 npm
    6
    MIT