LogicProMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_statusA | Show the local Logic extension bridge status. |
| list_logic_tracksA | List Logic tracks currently visible through inserted LogicProMCP extensions. |
| read_logic_trackC | Read MIDI events captured from one Logic-side bridge instance. |
| read_all_logic_tracksA | Read all MIDI events captured from all inserted Logic-side bridge instances. |
| read_midi_fileC | Read a Standard MIDI File exported from Logic Pro. |
| create_midi_regionC | Create a Logic-importable MIDI region from a short musical prompt. |
| create_drum_regionC | Create a drum MIDI region on channel 10. |
| create_chord_regionC | Create a chord progression MIDI region. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: status, creating specific types of MIDI regions, listing tracks, and reading MIDI events from different sources. There is no overlap or ambiguity.
Most tools use a consistent verb_noun pattern with underscores (e.g., create_chord_region, list_logic_tracks). However, 'bridge_status' breaks the pattern by having no verb, causing minor inconsistency.
With 8 tools, the server is well-scoped for its purpose of interacting with Logic Pro's MIDI capabilities. Each tool serves a necessary role without being overwhelming or insufficient.
The tool set covers creation and reading of MIDI regions and tracks, but lacks update and delete operations. This gap may hinder workflows that require modifying or removing existing elements.