The MCP server is an early preview. Functionality may change.
Installing for Claude Desktop
Go to Help → Install Claude Extension in Gridshift’s menu bar. This installs the MCP server as an extension in Claude Desktop.
Adding to Other Clients
The MCP server uses a bridge binary that communicates with Gridshift via Unix socket. Add the following to your client’s MCP configuration:
{
"mcpServers": {
"gridshift": {
"command": "/Applications/Gridshift.app/Contents/Helpers/GridshiftBridge"
}
}
}
Session
| Tool | Description |
|---|
get_session_overview | Get project info, transport state, tracks, and mixer levels in one call. Use the include parameter to request specific sections. |
Transport
| Tool | Description |
|---|
transport_control | Control playback, recording, loop, tempo — all via a single action parameter (play, stop, toggle_playback, toggle_loop, toggle_recording, go_to_beginning, set_tempo). |
Tracks
| Tool | Description |
|---|
track_add | Add a sample or instrument track. |
track_configure | Set volume, pan, mute, and solo for one or more tracks in a single call. Accepts a batch operations array. |
track_rename | Rename a track. |
Plugins
| Tool | Description |
|---|
available_plugins | Search installed AU plugins by name or manufacturer. |
plugins_list | List all loaded plugins across tracks with bypass state and parameter count. |
plugin_get_parameters | Get plugin parameters with type metadata, value labels, and pagination. |
plugin_configure | Set parameter values and/or toggle bypass in a single call. |
plugin_add_remove | Add or remove plugins on tracks. Supports batch operations across multiple tracks. |
Clips & MIDI
| Tool | Description |
|---|
clip_delete | Delete clips by ID or clear all clips on a track. Works with any clip type. |
midi_clip_create | Create a MIDI clip with optional initial notes. Returns the clip ID for further editing. |
midi_clip_read | Read all notes from a MIDI clip (pitch, position, duration, velocity). |
midi_clip_edit | Add, delete, or modify notes in a MIDI clip. Supports batch operations. |
Design Principles
Gridshift’s MCP tools follow best practices for LLM integration:
- Workflow-oriented: Tools map to user goals, not internal APIs.
- Compound operations: Batch changes in single round-trips (e.g. configure multiple tracks at once).
- Rich metadata: Plugin parameters include type info and human-readable labels so the AI can set values correctly without trial-and-error.
- Musical context: Project key and scale are included in the session overview so the AI writes in-key MIDI.
