Model Context Protocol moderate risk

Melrose

The melrose-mcp server allows for programmatic music creation and playback using the Melrōse language, offering tempo control and device selection.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteexec

Quickstart

Config

{
    "mcpServers": {
        "melrōse": {
          "command": "<YOUR DIRECTORY TO THE BINARY>/melrose-mcp",
          "args": []
        }
    }
}

Exposed MCP Tools (4)

moderate

melrose_play

Plays a musical expression written in the Melrōse language.

Can execute arbitrary Melrōse code, potentially leading to unexpected sounds or resource usage.

safe

melrose_bpm

Changes the tempo (beats per minute) of the music playback.

Modifies a playback parameter; no destructive actions.

safe

melrose_devices

Lists the available MIDI output devices.

Read-only operation; no side effects.

moderate

melrose_change_output_device

Changes the current MIDI output device.

Modifies the output destination, potentially directing sound to unintended devices.

Safety Assessment

The melrose-mcp server is relatively safe for music creation, but the ability to execute arbitrary Melrōse code introduces some risk. Ensure that the client application using this server has appropriate safeguards to prevent malicious or resource-intensive code from being executed.

No direct filesystem access
Limited execution capabilities within the Melrōse environment
Requires a MIDI receiver setup, adding a layer of separation
No inherent network exposure beyond the client-server MCP connection

Can execute arbitrary Melrōse code, potentially leading to unexpected sounds or resource usage
No explicit sandboxing is mentioned
The `melrose_change_output_device` tool could potentially direct output to unintended devices
Lack of input validation on Melrōse expressions could lead to issues