mcp-score

Overview Schema Source Related Servers Discussions Admin

connect_to_musescore

Establish a live WebSocket connection to MuseScore Studio (4.4.2+) to enable real-time score creation and editing via the MCP Score Bridge plugin. Specify host and port for remote or default localhost.

Instructions

Connect to a running MuseScore Studio (4.4.2 or later).

The MCP Score Bridge plugin must be running in MuseScore with its window open. Connecting disconnects any other application.

Args: host: WebSocket host (default: localhost). port: WebSocket port (default: 8765).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`host`	No		localhost
`port`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 26, 2026
- addedOutput schema / $defs
```
Added value: +{
+  "CommandResult": {
+    "additionalProperties": true,
+    "type": "object"
+  }
+}
```
- addedOutput schema / properties / result / $ref
```
Added value: +"#/$defs/CommandResult"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / properties / result / type
```
Removed value: -"string"
```
First observedv0.1.0May 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses a meaningful side effect ('Connecting disconnects any other application') and a runtime prerequisite. It does not describe failure modes, but the core behavioral traits are covered.

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

Conciseness5/5

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

The description is compact and well-organized: purpose, prerequisite, side effect, then arguments. Every sentence earns its place, and important warnings are front-loaded before the parameter list.

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

Completeness5/5

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

For an optional-parameter connection tool with an output schema, the description covers the version requirement, plugin prerequisite, side effects, and both parameters. Nothing an agent needs to call this tool correctly is missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description compensates by documenting both parameters. It adds WebSocket context to host and port beyond the schema titles and repeats defaults, which is adequate for these simple optional parameters.

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

Purpose5/5

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

States a specific verb ('Connect') and a specific resource ('running MuseScore Studio (4.4.2 or later)'), and names the required plugin. The MuseScore resource clearly distinguishes it from sibling tools like connect_to_dorico.

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

Usage Guidelines4/5

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

Provides clear context by stating the plugin must be running with its window open, and warns that connecting disconnects any other application. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to know when to invoke it.

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