Skip to main content
Glama
Sign In
enesjakozh
Cursor Sound MCP

Cursor Sound MCP

by yarikbuilds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sonido del cursor MCP

Una implementación del Protocolo de Contexto de Modelo (MCP) que reproduce efectos de sonido después de que Cursor AI complete la generación de código. Este MCP se integra con Cursor para proporcionar retroalimentación de audio y ofrecer una experiencia de codificación más interactiva.

Características

  • Reproduce un efecto de sonido cuando el cursor completa la generación de código

  • Utiliza el Protocolo de Contexto de Modelo (MCP) para la integración estandarizada

  • Efectos de sonido configurables

Related MCP server: MCP Sound Tool

Instalación

  1. Instalar dependencias:

npm install

  1. Añade tus efectos de sonido: Coloca tus archivos de sonido en el directorio sounds . El sonido predeterminado esperado es:

  • sounds/completion.mp3 - Se reproduce después de la generación del código

Puedes encontrar efectos de sonido gratuitos en freesound.org.

  1. Construir el proyecto:

npm run build

Uso

Ejecute el servidor MCP:

npm start

El servidor se iniciará y escuchará eventos del Cursor a través del transporte stdio.

Configuración

Los efectos de sonido y el volumen se pueden personalizar mediante:

  1. Reemplazo de los archivos de sonido en el directorio sounds

  2. Modificar las rutas de los archivos de sonido en src/index.ts

Desarrollo

Para el desarrollo con recompilación automática:

npm run dev

Available Tools

1 tool
playCompletionSoundD
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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

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 recent community 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
    9 npm
    6
    MIT