VS Code installation

Install Logic Pro MCP in VS Code.

This guide uses VS Code's mcp.json format: a servers object in the user profile or .vscode/mcp.json in the workspace. Copilot's portable .mcp.json uses a different mcpServers format.

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.
  • Use a VS Code release with MCP server support and decide whether the registration belongs to the user profile or current workspace.

Verified path

Install and verify

  1. 01

    Install the server package

    Install Logic Pro MCP from its versioned Homebrew distribution before editing the editor profile.

    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

    Open the intended MCP file

    Run MCP: Open User Configuration for profile scope, or create .vscode/mcp.json for workspace scope.

  3. 03

    Add the VS Code stdio server

    Merge this object into the configuration. The documented VS Code root key is servers and a local process can declare type stdio.

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

    Review workspace trust

    Review the workspace and server command before trusting it. Workspace servers inherit Workspace Trust; servers from other sources can require a separate trust decision.

  5. 05

    Authorize VS Code as parent

    Grant the editor—not merely Terminal—the TCC capabilities required by the child process, then rerun the permission probe.

    LogicProMCP --check-permissions
  6. 06

    Read the server output

    Run MCP: List Servers, select logic-pro, and choose Show Output. Resolve executable lookup or protocol errors there before testing Logic.

    LogicProMCP doctor --profile core --client vscode

Observable evidence

What success means

MCP: List Servers reports logic-pro running, Show Output has no startup error, and the vscode Doctor profile resolves all required local checks.

Current boundary

What this does not prove

A workspace can be untrusted or use a different profile than expected. A working user-profile entry does not prove a separate workspace definition was approved.

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