How the local integration connects. Diagram only; this is not a Logic Pro screenshot or live session.
Built around your workflow
A conversation beside your session.
A bridge between the way you describe a production task and the Logic session in front of you. Your MCP client talks to a server on your Mac, which works with Logic through supported MIDI, OSC and macOS interfaces.
01
Move around your session.
Use the documented transport, track selection and mixer operations to navigate and balance a project. The visible MCU surface covers eight tracks; banking is not reliable, and some operations use Accessibility fallback.
02
Make deliberate changes.
Adjust supported plug-in controls, MIDI and commands where Logic exposes them. Ambiguous controls should refuse rather than guess. Results are reported as confirmed, uncertain or failed; confirmed means read back according to the project’s contract.
03
Prepare your delivery.
Work with documented bounce, stems, measurement and leveling workflows. Optional upload requires your own configured rclone destination. Camera-based hands control and voice workflows are separate advanced setups with extra dependencies and permissions.
The first steps
Set up locally. Stay in your flow.
Keep the README as your installation reference. Logic version, UI layout and plug-in coverage can affect behavior; review the project’s current compatibility and troubleshooting notes before use.
Clone the public repository and install its Python environment with uv sync.
02
Run the project’s doctor checks to inspect the local setup.
03
Grant Accessibility and Automation permissions to the process running the server.
04
Register the server in your MCP client and use it with Logic Pro on the same Mac.
Good to know
A few honest answers.
Can I control Logic from a hosted or Linux server?
Actual control needs a local Mac and Logic Pro. Hosted/Linux inspection mode exposes schemas and inspection information only; it cannot control a Logic session.
Does confirmed mean the action definitely happened?
Confirmed means the project read the result back according to its documented contract. Other outcomes can be uncertain or failed. Review the returned status and the session, especially before continuing a larger workflow.
Do I need a camera or a voice setup?
No. Gesture and voice control are optional advanced features, separate from the basic MCP setup. Camera permission and additional dependencies apply when enabling those features.
Is a ready-to-install app available?
Release v0.1.1 does not include a standalone installer. Source code, environment setup and the doctor checks are available on GitHub.
Will every Logic version and plug-in work?
Support varies with the Logic version, UI layout and plug-in. Check the README’s compatibility notes and verify returned changes in your session. Ambiguous or unsupported controls may refuse the request.
Source, setup & support
Make it part of your setup.
Start with the source and current setup documentation. These MCP integrations require a local developer setup; standalone app installers are not available.
