LogicProMCP
Integration with Apple Logic Pro for reading and writing MIDI track data, enabling AI-assisted music generation and editing through the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LogicProMCP create a four bar chord progression in C major"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
Insert a
LogicProMCP BridgeAUv3 MIDI FX plugin on every MIDI/software-instrument track that should be readable.Each plugin instance sends captured MIDI events to the local MCP sidecar.
The MCP server exposes the aggregated result as "all Logic tracks."
Generated MIDI can be written as
.midfiles 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.midfile 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
logicpromcpFor 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.midLogic 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.midpath toread_midi_file.To write a new track/region: run
create_midi_region, then drag the generated.midfile into Logic or useFile > 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 toolsbridge_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
Scored across 8 tools
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.
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.
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.
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
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
MCP server for Producer/Riffusion AI music generation
MCP server for progressive tool usage at any scale (see https://klavis.ai)
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that bridges Ableton Live with AI models, enabling real-time project inspection and control such as track overview, device parameters, and audio analysis.1236 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceEnables an AI assistant to control Apple Logic Pro DAW including transport, mixing, playhead positioning, MIDI region read/write, and more, via MCP.4-
- AlicenseNot gradedqualityDmaintenanceA minimal MCP server that composes MIDI, loads Logic Pro factory patches (including Alchemy), and drives transport, turning Logic Pro into an AI-playable instrument.2MIT
- AlicenseBqualityDmaintenanceLocal 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.5918 npmMIT