Cursor installation

Install Logic Pro MCP in Cursor.

Cursor accepts local stdio servers under an mcpServers object. Choose global scope for every workspace or .cursor/mcp.json for one repository.

Before you begin

Prerequisites

macOS 14 or later; Logic Pro 12.3 is actively validated, with 12.0.1 and later best-effort.
Choose one Cursor scope: ~/.cursor/mcp.json globally, or .cursor/mcp.json inside the intended project.

Verified path

01
Install the local binary
Use the tagged Homebrew tap and verify installation before opening Cursor's settings.
```
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
Choose the JSON location
Create the global file for all projects or the workspace file for a repository-specific server.
```
mkdir -p "$HOME/.cursor"
open -a TextEdit "$HOME/.cursor/mcp.json"
```
03
Register the Cursor server
Merge this server into the root mcpServers map. Cursor's schema uses mcpServers, command, args, and optional env fields.
```
{
  "mcpServers": {
    "logic-pro": {
      "command": "LogicProMCP",
      "args": []
    }
  }
}
```
04
Enable the exposed tools
Open Cursor Settings → Tools & MCP, confirm the server is enabled, and review the listed tools before allowing agent use.
05
Grant Cursor's permissions
Because Cursor spawns the child process, authorize Cursor for Accessibility, Logic Pro Automation, System Events Automation, and Input Monitoring as requested.
```
LogicProMCP --check-permissions
```
06
Diagnose a red indicator
Check Tools & MCP for the startup error, verify that the JSON is valid, then run the client-specific readiness profile.
```
LogicProMCP doctor --profile core --client cursor
```

Observable evidence

Cursor Settings shows logic-pro enabled with its tools available, and Doctor has no unresolved required check for the cursor profile.

Current boundary

Enabling a tool in Cursor proves discovery, not that Logic accepted a later UI mutation or that its state was read back.

Primary evidence

Product behavior is pinned to the v3.11.0 source. Client registration details remain owned by the client vendor.

Continue