Skip to main content
Glama

LogicProMCP

LogicProMCP is a local Model Context Protocol server plus a planned Logic Pro MIDI FX bridge for working with Logic Pro MIDI material.

The intended Logic integration is:

  1. Insert a LogicProMCP Bridge AUv3 MIDI FX plugin on every MIDI/software-instrument track that should be readable.

  2. Each plugin instance sends captured MIDI events to the local MCP sidecar.

  3. The MCP server exposes the aggregated result as "all Logic tracks."

  4. Generated MIDI can be written as .mid files first, then later sent back through a virtual MIDI/AUv3 output path.

Logic Pro does not currently expose a public project API that lets one local service directly enumerate every track and MIDI region in an open project. "Read all tracks automatically" therefore means "read all tracks that have the bridge extension inserted," ideally through a saved Logic template.

Tools

  • bridge_status: show the local Logic bridge receiver.

  • list_logic_tracks: list tracks reported by Logic-side bridge instances.

  • read_logic_track: read captured MIDI from one bridge instance.

  • read_all_logic_tracks: read captured MIDI from all bridge instances.

  • read_midi_file: inspect a Standard MIDI File exported from Logic.

  • create_midi_region: create a new single-region .mid file from a musical prompt.

  • create_drum_region: create a drum pattern region.

  • create_chord_region: create a chord progression region.

Related MCP server: logic-pro-mcp

Install

cd /Users/shlomy/GIT_Repos/LogicProMCP
python3 -m venv .venv
. .venv/bin/activate
python -m pip install -e .

Run MCP Server

logicpromcp

For Claude Desktop or another MCP client, configure the command as:

{
  "mcpServers": {
    "logicpro": {
      "command": "/Users/shlomy/GIT_Repos/LogicProMCP/.venv/bin/logicpromcp"
    }
  }
}

CLI Smoke Test

logicpromcp-midi create --prompt "four bar funky bass line in C minor" --out examples/funky_bass.mid
logicpromcp-midi inspect examples/funky_bass.mid

Logic Workflow

  • To read live/playback material from Logic: run logicpromcp, then insert the AUv3 bridge on every track that should be visible to the MCP server.

  • To read exported material: select regions in Logic, use File > Export > Selection as MIDI File, then pass that .mid path to read_midi_file.

  • To write a new track/region: run create_midi_region, then drag the generated .mid file into Logic or use File > Import > MIDI File.

  • To preserve tempo and bar alignment, create generated regions at the same BPM and bar length as the Logic project.

See docs/LOGIC_EXTENSION.md for the extension bridge contract.

Roadmap

  • AUv3 MIDI FX listener for live MIDI capture per inserted track.

  • Virtual MIDI output for recording generated MIDI directly into Logic.

  • AppleScript/Shortcuts helper for importing generated MIDI into the frontmost Logic project.

  • Region metadata sidecar files for round-tripping track names, bar ranges, prompts, and model decisions.

Available Tools

8 tools
bridge_statusA

Show the local Logic extension bridge status.

Inputs: no named parameters. Returns: object

create_chord_regionC

Create a chord progression MIDI region.

Inputs: bpm, key, bars, channel, +1 more. Returns: object

create_drum_regionC

Create a drum MIDI region on channel 10.

Inputs: bpm, bars, prompt, output_dir. Returns: object

create_midi_regionC

Create a Logic-importable MIDI region from a short musical prompt.

Inputs: prompt (required), bpm, key, bars, +3 more. Returns: object

list_logic_tracksA

List Logic tracks currently visible through inserted LogicProMCP extensions.

Inputs: no named parameters. Returns: object

read_all_logic_tracksA

Read all MIDI events captured from all inserted Logic-side bridge instances.

Inputs: no named parameters. Returns: object

read_logic_trackC

Read MIDI events captured from one Logic-side bridge instance.

Inputs: instance_id (required). Returns: object

read_midi_fileC

Read a Standard MIDI File exported from Logic Pro.

Inputs: path (required). Returns: object

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: status, creating specific types of MIDI regions, listing tracks, and reading MIDI events from different sources. There is no overlap or ambiguity.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern with underscores (e.g., create_chord_region, list_logic_tracks). However, 'bridge_status' breaks the pattern by having no verb, causing minor inconsistency.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose of interacting with Logic Pro's MIDI capabilities. Each tool serves a necessary role without being overwhelming or insufficient.

    Completeness3/5

    The tool set covers creation and reading of MIDI regions and tracks, but lacks update and delete operations. This gap may hinder workflows that require modifying or removing existing elements.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A minimal MCP server that composes MIDI, loads Logic Pro factory patches (including Alchemy), and drives transport, turning Logic Pro into an AI-playable instrument.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Local MCP server for inspecting and controlling Ableton Live through a local HTTP bridge. Enables LLMs to perform production workflows like MIDI import, track editing, mixing, mastering, and export.
      59
      18 npm
      MIT