Skip to main content
Glama
Sign In
Vibe Composer MIDI MCP

Vibe Composer MIDI MCP

by mikeborozdin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vibe-composer-midi-mcp

  • Vibe composer as an MCP server

  • Watch the video for an overview

  • Talk to an LLM and compose music!

  • Multi track - not just a piano, but the whole band

  • Also can output to a software or a hardware synthesizer for a better sound!

Complete example on YouTube

Complete example

Example prompts

Playing it on a software or hardware synthesizer

  • Ask an LLM to list MIDI outputs - Which MIDI outputs are available?

    • It may tell you that you have Logic Pro

  • Then ask to play it on logic pro and assign channels: e.g.:

Play in on Logic Pro and route the tracks to the following channels:

- Piano - channel 0
- Sax - channel 1
- Drums - channel 2

Installation

  • Using an example of Claude Desktop as an MCP client:

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json

"vibe-composer-midi-mcp": {
  "command": "npx",
  "args": ["vibe-composer-midi-mcp@latest"]
}

Available Tools

2 tools
list-midi-outputsList MIDI outputsC

Lists MIDI outputs

Inputs: no named parameters.

playPlay a music scoreC

Plays a music score

Inputs: bpm (required), tracks (required), midiOuputName.

Tool Schema Changelog

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

Loading tool schema changelog…

    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

    C2.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists MIDI outputs (a discovery/query function), and the other plays a music score (an action/execution function). There is no overlap or ambiguity between them.

    Naming Consistency2/5

    The naming is inconsistent: 'list-midi-outputs' uses kebab-case with a verb-noun structure, while 'play' is a single verb without a noun. This mix of conventions lacks a predictable pattern.

    Tool Count2/5

    With only 2 tools, the server feels too thin for a 'Vibe Composer MIDI' domain, which suggests music composition or playback. Key operations like creating, editing, or stopping scores are missing, making the set underpowered.

    Completeness2/5

    The tool surface is severely incomplete for MIDI composition/playback. There are no tools to create, edit, save, load, or stop scores, and no control over playback (e.g., pause, volume). This will cause agent failures in typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • MCP MIDI Bridge

      tezza1971
      A
      license
      Not graded
      quality
      D
      maintenance
      An Electron desktop application that bridges LLM-driven music generation with DAWs by converting NoteSequence JSON from AI models into MIDI data that can be played, recorded, and manipulated in any digital audio workstation.
      4
      Apache 2.0

    • MaestroMCP

      vbarreiratt
      -
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to control MIDI devices and synthesizers through WebMidi.js integration. Provides tools for sending notes, control changes, creating virtual ports, and executing complex musical sequences.
      11
      -

    Appeared in Searches