Open-source Logic Pro control plane

Give your agent a signal path into Logic Pro.

A local MCP server for Claude, Cursor, VS Code, and custom agents to compose, control, inspect, and verify real work in Logic Pro.

View on GitHub Install with Homebrew

stable v3.11.0 · macOS 14+ · Logic Pro 12.3 first-class · MIT

SESSION / SIGNAL_01 CONNECTED
REQUEST

“Build an 8-bar ambient loop at 92 BPM.”

01INPUT
02READ
03ACT
04VERIFY
STATECONFIRMED
TEMPO92.00 BPM
REGIONS03 LIVE
10MCP tools
18read resources
11resource templates
7native channels
2,271deterministic tests

From intent to evidence

Automation you can hear.
State you can trust.

Each operation routes through the strongest available macOS channel, then exposes what Logic Pro actually did.

01 / COMPOSE

Turn prompts into playable sessions.

Create instrument and Drummer tracks, generate MIDI sequences, assign patches, set tempo, and play back the result.

02 / VERIFY

Know what happened after the write.

High-risk operations carry target identity, confirmation level, readback, and a typed outcome.

STATE ACONFIRMED
STATE BUNCERTAIN
STATE CFAILED
03 / DELIVER

Plan, export, and inspect audio artifacts.

Dry-run export plans, resume interrupted batches, and analyze the files Logic Pro produced.

A broader control surface

One interface.
Seven native channels.

MCU, Accessibility, AppleScript, CoreMIDI, CGEvent, Scripter, and MIDI Key Commands are routed behind a compact MCP surface.

01

COMPOSE

Create tracks, write MIDI, set instruments, and shape tempo from an agent prompt.

02

CONTROL

Operate transport, navigation, mixer state, and project lifecycle with explicit targets.

03

READ

Inspect transport, tracks, mixer, markers, project metadata, inventory, and readiness as resources.

04

VERIFY

Return confirmed, uncertain, or failed outcomes instead of turning automation into guesswork.

Architecture at a glance

Compact outside.
Purpose-built inside.

The Swift stdio server validates intent, chooses the strongest channel, then publishes cached or live evidence through resources.

  1. 01MCP CLIENT

    Claude, Cursor, VS Code, or a custom agent launches the local stdio server.

  2. 02DISPATCH

    Ten compact tools validate command parameters and safety requirements.

  3. 03ROUTE

    ChannelRouter selects the strongest available native control channel.

  4. 04READ BACK

    Resources return state with source, freshness, and evidence labels.

01
COMPOSE

logic_tracks · logic_midi

Create tracks, write and import MIDI, resolve instruments, and manage ports.

02
CONTROL

logic_transport · logic_edit · logic_navigate

Run transport, edit regions, move by bar or marker, and control views.

03
MIX

logic_mixer · logic_plugins

Set level and pan, inspect stock plugins, and perform guarded verified apply-back.

04
DELIVER

logic_project

Open, save, audit, bounce, plan exports, and resume interrupted batches.

05
OBSERVE

logic_audio · logic_system

Analyze exported audio and report health, channels, permissions, and readiness.

Tools act. Ten compact tools expose 99 public commands. Resources read without mutating Logic, while prompts package ten built-in workflows from readiness and composition to gain staging, cleanup, bounce, and batch export.

Fail closed by design

Honest when the UI is not.

Targets are explicit. Destructive flows require confirmation. Unreadable or unverified state is returned as uncertain or failed, never promoted to success.

Doctor scopes readiness to core, mixer, keycmd, legacy-scripter, or full, then adapts checks for Claude, Cursor, VS Code, terminal, or custom hosts.

Read the trust model
LOGICPRO MCP / DOCTORPROFILE: CORE
$ LogicProMCP doctor --profile core

✓ binary.path                 ready
✓ permissions.accessibility  granted
✓ logic.running               detected
✓ channel.mcu                 ready
✓ channel.accessibility       ready

STATUS  ready · 5/5 capabilities

HONEST ENVELOPES

Every mutation returns confirmed, uncertain with a reason, or failed with an error.

EXACT TARGETS

Track, marker, mixer, MIDI import, and plugin writes validate explicit targets before acting.

VERIFIED APPLY-BACK

Plugin State A requires project, track, slot, identity, and post-write readback to agree.

CONFIRMATION LEVELS

Destructive project flows and plugin insertion require explicit confirmation metadata.

PROVENANCE

Read surfaces label source, freshness, and evidence so agents do not have to guess.

HARDENED DELIVERY

Homebrew pins release SHA256; shell installs fail closed without explicit trust pins.

Claims tied to evidence

Stable v3.11.0.
No green by implication.

Release claims stay attached to shipped artifacts, deterministic tests, targeted live QA, or explicitly linked historical evidence.

2,271Swift tests

Current source tree deterministic suite: passed with zero failures.

372 / 373strict live E2E

Last full Logic Pro 12.3 run on the v3.8 line: 372 passed, one skipped, zero failed.

UNIVERSALrelease artifacts

arm64 and x86_64 archives with SHA256SUMS and release metadata.

TARGETEDcurrent live QA

Tempo fallback, native Bounce, partial regions, markers, Count In, Step Input, and help categories.

STABLE / v3.11.0

Latest Logic Pro first. Logic Pro 12.3 is actively validated; versions down to 12.0.1 remain best-effort. Desktop Logic Pro and Creator Studio are both resolved by bundle identity.

Release evidence ↗

Start with a verified install

From zero to ready.

Install the universal binary, register your client, verify macOS permissions, then let Doctor order the remaining work.

01

Install

brew tap MongLong0214/logic-pro-mcp \
  https://github.com/MongLong0214/logic-pro-mcp
brew trust monglong0214/logic-pro-mcp
brew install logic-pro-mcp
02

Register

claude mcp add --scope user \
  logic-pro -- LogicProMCP
03

Permissions

LogicProMCP --check-permissions

Checks Accessibility, Automation to Logic Pro and System Events, plus PostEvent/Input Monitoring.

04

Diagnose

LogicProMCP doctor \
  --profile core \
  --client claude-code

Full setup registers the LogicProMCP-MCU-Internal control surface. Scripter is optional unless you need legacy plugin-parameter writes.

Boundaries, not footnotes

Known limitations,
published plainly.

Where Logic Pro cannot provide faithful readback, the server constrains the operation or refuses the claim.

01Tempo input

Exact AX slider fallbacks are bounded and fail closed when Logic cannot confirm the requested tempo.

02MIDI region padding

Imported regions may visually extend from bar 1 to the target bar; note timing remains exact.

03External MIDI bounce

Unverified GM Device or External MIDI regions block a claimed audible bounce.

04Key Commands

Logic 12.2+ requires Manual MIDI Learn because the legacy plist is no longer auto-imported.

05Markers

Unreadable state stays unreadable or cached; rename_marker remains not implemented.

06Plugin parameters

Unsupported live parameter readback remains limited and fails closed.

Go to the source

Docs for every stage.

From first launch to API contracts, threat modeling, troubleshooting, and contribution.

SETUP

Install, permissions, MCP registration, Logic integration, and Doctor remediation.

API

All tools, resources, templates, Honest Contract, and verified apply-back.

TROUBLESHOOT

Common client, permission, channel, and Logic Pro failures with fixes.

SECURITY

Threat model, installer trust tiers, hardening, and private disclosure.

CHANGELOG

Stable release history, deferred work, and evidence-linked changes.

CONTRIBUTE

Development setup, scoped PR workflow, verification, and open issues.

Logic Pro MCP FAQ

Before you install.

Direct answers for musicians, developers, and AI agents evaluating the server.

What is Logic Pro MCP?

Logic Pro MCP is an open-source local Model Context Protocol server that lets compatible AI clients compose, control, inspect, and verify work in Logic Pro on macOS.

Which AI clients can use it?

It works with MCP clients that can launch a local stdio server, including Claude Code, Claude Desktop, Cursor, VS Code, and custom agents.

What can an AI agent control in Logic Pro?

Agents can create tracks and MIDI, operate transport and navigation, inspect mixer and project state, manage project workflows, analyze exported audio, and verify high-risk writes.

How do I install Logic Pro MCP?

Install the universal binary with the Homebrew tap, register LogicProMCP with your MCP client, grant the required macOS permissions, and run LogicProMCP doctor to verify readiness.

Is Logic Pro MCP free?

Yes. The project is open source under the MIT License, and its source, releases, setup guide, API reference, security policy, and issue tracker are public on GitHub.

Build with the signal, not the screen

Make Logic Pro agent-ready.

Explore the repository