Local MCP server for stateful, fail-closed Logic Pro control and live project readback.
Connect Logic Pro MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local MCP server for stateful, fail-closed Logic Pro control and live project readback. The logic pro mcp mcp server is what makes that connection.
A local Model Context Protocol (MCP) server that lets Claude Code, Claude Desktop, Cursor, VS Code, and custom AI agents control Logic Pro for AI music production: create tracks, write MIDI, operate transport and mixer state, inspect live project data, and verify results.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Fail — closed targets**: dangerous mixer, marker, track, MIDI import, and plugin operations require explicit targets and validationSurface — Current source treeArea — What agents can doTransport — Play, stop, record, locate, cycle, metronome, tempoTracks — Create, delete, duplicate, select, rename, mute, solo, arm, set instrumentsMixer — Volume, pan, plugin snapshots, guarded stock plugin insertionLibrary — Scan Logic's instrument library and load patches by pathNavigation — Bars, markers, zoom, view togglesDocument — AudienceGate — Current evidenceSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: LOGIC_PRO_BUNDLE_ID, LOGIC_PRO_MCP_TEAM_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Logic Pro MCP's toolset — Fail, Surface, Area and 7 more — is a fair guide to whether it matches your workflow. It is maintained by MongLong0214; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Logic Pro MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Fail | closed targets**: dangerous mixer, marker, track, MIDI import, and plugin operations require explicit targets and validation. |
| Surface | Current source tree |
| Area | What agents can do |
| Transport | Play, stop, record, locate, cycle, metronome, tempo |
| Tracks | Create, delete, duplicate, select, rename, mute, solo, arm, set instruments |
| Mixer | Volume, pan, plugin snapshots, guarded stock plugin insertion |
| Library | Scan Logic's instrument library and load patches by path |
| Navigation | Bars, markers, zoom, view toggles |
| Document | Audience |
| Gate | Current evidence |
Generic MCP client config:
```json
{
"mcpServers": {
"logic-pro": {
"command": "LogicProMCP"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOGIC_PRO_BUNDLE_ID | Configuration value read at startup. | Optional |
| LOGIC_PRO_MCP_TEAM_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.