Claude Code installation
Install Logic Pro MCP for Claude Code.
Claude Code has a documented CLI registration path. The separator matters: Claude options precede the server name, and the executable follows --.
Before you begin
Prerequisites
- macOS 14 or later; Logic Pro 12.3 is actively validated, with 12.0.1 and later best-effort.
- Install the signed universal binary from the project Homebrew tap.
Verified path
Install and verify
- 01
Install the executable
Add the project tap, approve that tap explicitly, and install the published formula.
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
Create a user-scoped server
Register one local stdio server for every Claude Code project owned by this macOS user.
claude mcp add --scope user logic-pro -- LogicProMCP - 03
Inspect Claude's registration
Use Claude Code's management command to confirm the resolved command and scope before troubleshooting Logic.
claude mcp get logic-pro - 04
Authorize the launcher
Grant Accessibility plus Automation access for Logic Pro and System Events to the process that launches Claude Code, then inspect all four permission probes.
LogicProMCP --check-permissions - 05
Open the MCP status panel
Start Claude Code and run /mcp. The server must appear connected before its tools can be selected.
LogicProMCP doctor --profile core --client claude-code - 06
Recover a stale entry
If the command or scope is wrong, remove the named entry and add it again with options before the server name.
claude mcp remove logic-pro claude mcp add --scope user logic-pro -- LogicProMCP
Observable evidence
What success means
Claude Code reports logic-pro as connected in /mcp, while Doctor reports the required core checks for the claude-code launch profile.
Current boundary
What this does not prove
A passing Terminal probe cannot grant or prove permissions for a different app that later launches the server.
Primary evidence
Verify at the source
Product behavior is pinned to the v3.11.0 source. Client registration details remain owned by the client vendor.
Continue