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.

View source on GitHubFollow the workflow

Before you begin

Prerequisites

  • macOS 14+ for the server. Logic Pro 13.0 is the declared current version; the supported floor is 12.0.1, on a best-effort basis. Desktop Logic Pro is supported; Creator Studio is recognized, not supported.
  • Choose one Cursor scope: ~/.cursor/mcp.json globally, or .cursor/mcp.json inside the intended project.

Verified path

Install and verify

  1. 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
  2. 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"
  3. 03

    Register the Cursor server

    Merge this server into the root mcpServers map. Declare type stdio for the local process, with command and args inside the mcpServers map.

    {
      "mcpServers": {
        "logic-pro": {
          "type": "stdio",
          "command": "LogicProMCP",
          "args": []
        }
      }
    }
  4. 04

    Enable the exposed tools

    Open Customize in the sidebar, enable logic-pro, and review its available tools before agent use.

  5. 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
  6. 06

    Diagnose a red indicator

    Open the Output panel and select MCP Logs to inspect startup errors. Check the JSON and executable path, then run the client-specific readiness profile.

    LogicProMCP doctor --profile core --client cursor

Observable evidence

What success means

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

Current boundary

What this does not prove

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

Primary evidence

Verify at the source

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

Continue

Related verified paths