Claude Desktop installation

Install Logic Pro MCP for Claude Desktop.

Claude Desktop reads local server definitions from its macOS configuration file. A full application restart is required after changing that file.

View source on GitHub Follow the workflow

Before you begin

Prerequisites

macOS 14 or later; Logic Pro 12.3 is actively validated, with 12.0.1 and later best-effort.
Quit Claude Desktop before editing its local MCP configuration; preserve any existing mcpServers entries.

Verified path

Install and verify

01
Install Logic Pro MCP
Install the universal server first so Claude Desktop can resolve the configured executable.
```
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
Locate the Desktop config
Open Settings → Developer → Edit Config, or inspect the documented macOS file directly.
```
open -a TextEdit "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
```
03
Add the stdio definition
Merge this exact mcpServers member into the existing JSON object; do not overwrite unrelated servers.
```
{
  "mcpServers": {
    "logic-pro": {
      "command": "LogicProMCP",
      "args": []
    }
  }
}
```
04
Restart the desktop host
Quit Claude Desktop completely and reopen it so the local process is spawned from the new definition.
05
Grant Desktop-owned access
Approve Accessibility and both Automation targets for Claude Desktop, the parent application that starts the stdio child.
```
LogicProMCP --check-permissions
```
06
Inspect server logs
If tools are absent, inspect Claude's MCP logs and look for a command-not-found or JSON parse error before changing Logic settings.
```
open "$HOME/Library/Logs/Claude"
LogicProMCP doctor --profile core --client claude-desktop
```

Observable evidence

What success means

Claude Desktop exposes the logic-pro tools after a full restart, and its MCP log contains no launch or JSON configuration error.

Current boundary

What this does not prove

Claude Desktop Extensions and raw local JSON are separate installation mechanisms. This route documents the MCP standard's local configuration path, not an .mcpb extension package.

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.

Primary documentation Tagged setup guide

Continue

Prerequisites

Install and verify