Logic Pro MCP
Local MCP server for Logic Pro on macOS: an agent creates tracks, writes MIDI, runs the mixer and verifies the result
- 198 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Accessibility and Automation grants in macOS open control of Logic Pro and system events
- The agent changes and deletes tracks and data in the open project
Install
- Works in
Manual install
brew install logic-pro-mcpFirst `brew tap MongLong0214/logic-pro-mcp https://github.com/MongLong0214/logic-pro-mcp`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Accessibility and Automation grants in macOS open control of Logic Pro and system events
- The agent changes and deletes tracks and data in the open project
This is third-party code. Review the repository files before installing.
What it does
The server gives Claude Code, Cursor, Codex and other clients structured control of Logic Pro without brittle keyboard macros. Logic Pro has no first-party interface for agentic composition and the project fills the gap: ten tools (`logic_transport`, `logic_tracks`, `logic_mixer`, `logic_midi`, `logic_edit`, `logic_navigate`, `logic_project`, `logic_audio`, `logic_system`, `logic_plugins`) change state while resources only read. The agent creates tracks, writes MIDI parts, routes instruments, drives transport and the mixer and reads live project data. Server replies label evidence and do not present an uncertain outcome as success: if a result cannot be confirmed by readback it stays uncertain. It works through seven channels: CoreMIDI, Accessibility, CGEvent, AppleScript, MCU, MIDIKeyCommands and Scripter. In the repository example an 82 BPM lofi loop is composed entirely from prompts. Ten Logic Pro interface languages are supported.
Who it is for. Musicians and producers on a Mac who work in Logic Pro and want to sketch parts and set up a session by asking an agent.
Good fit when
- A four bar techno loop in A minor at 140 BPM is needed and the agent records the notes and picks drums
- A session is prepared in advance: tracks, instruments, tempo and markers
- Before mixing the agent reads mixer and project state and reports what does not add up
- An idea must be checked by ear at once: the agent starts playback and verifies the result
- Logic Pro is connected to an agent in Cursor or Codex without manual macros
Not a fit when
- You need a server for Ableton Live or another workstation: this one controls Logic Pro only
- Work is not on macOS: the server is written in Swift for macOS 14 and newer
- You need live audio capture with timbre judgment: the server handles MIDI, tracks and project state
Example request
Make a four bar techno loop in A minor at 140 BPM: a Roland TR-909 drum track and a bass partMCP
- Transport
- stdio
- Authentication
- not required
Limitations
You need macOS 14 or newer and Logic Pro, the latest version first. In privacy settings enable Accessibility for the app that launches the server and separately Automation for Logic Pro and System Events. Builds are ad hoc signed, so macOS asks for the grants again after every update. Known limits: a standalone `bounce` is not supported, tempo typing and plugin parameters are not verified everywhere and MIDI key commands cannot be read in Logic 12.2 and newer. The `LogicProMCP doctor` command shows readiness.
How to disable. Remove the server in the client (`claude mcp remove logic-pro`), clear the Accessibility and Automation grants in macOS settings and remove the package with `brew uninstall logic-pro-mcp`.
FAQ
How do I install Logic Pro MCP?
Run `brew tap MongLong0214/logic-pro-mcp https://github.com/MongLong0214/logic-pro-mcp` and then `brew install logic-pro-mcp`. A hash-verified installer also exists and is described in the README.
How do I connect it to Claude Code?
Run `claude mcp add --scope user logic-pro -- LogicProMCP`. Then `LogicProMCP --check-permissions` shows which macOS grants are given.
Which macOS permissions are needed?
Accessibility for the app that launches the server and Automation for Logic Pro and System Events as separate grants. They are given again after a build update.
What does the server do if a result cannot be confirmed?
The outcome stays uncertain and the reply says so. The agent sees which results are confirmed by reading the project back and which are not.
Is Logic Pro Creator Studio supported?
It is recognized but not supported. The main target is desktop Logic Pro with the `com.apple.logic10` identifier.
Discussion
No questions or reviews yet.
Related
MCP serversAn Ableton Live MCP server: 156 tools let Claude, Cursor or Codex write MIDI, load instruments and effects and mix a track.
An MCP server for Ableton Live: the agent creates tracks, places clips and builds arrangements straight in the open project
A local MCP server generates music and sound effects, builds loops, adjusts loudness and exports audio for games or video.
An MCP server with 181 tools: an agent writes MIDI, mixes and masters tracks in REAPER without sending the project to the cloud.
MCP Music Studio: music in chat with an agent
mcp-music-studio
An MCP server where an agent writes ABC sheet music or a Strudel live beat and the player with an editor opens in chat
flstudio-mcp: control FL Studio with Claude
flstudio-mcp
An MCP server with 72 tools for FL Studio 2025: mix diagnosis, plugins, piano roll, routing and MIDI export for Claude
README in short
The README lists the server surfaces: ten tools, 19 read resources and 12 templates, seven control channels and ten locales. Then come Homebrew and script installation, macOS permissions, the setup doctor, known limitations and development.