About Pro Tools Mcp
protools-mcp is a local MCP server for controlling and inspecting live Avid Pro Tools sessions through natural-language interactions with compatible assistants. It serves podcast post-production as well as music, broadcast, and audio post workflows, with transcript search and session editing tools.
Key features
- 01Inspect sessions, tracks, markers, and clips
- 02Search transcript CSV files with context
- 03Navigate the timeline and select regions
- 04Edit tracks and create markers
- 05Save, open, and version sessions
- 06Export selected tracks as AAF
Use cases
- 01Find transcript mentions by keyword or time range
- 02Review clips and markers in a Pro Tools session
- 03Adjust track states and add timeline markers
- 04Save session versions and export tracks
MCP support
The local MCP server exposes read and write tools for Pro Tools sessions to compatible MCP clients. It connects to a live session through the PTSL API, and write operations are confirmed before execution.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEprotools-mcp
A natural language interface for Avid Pro Tools, powered by Claude and the Model Context Protocol.
protools-mcp is a local MCP (Model Context Protocol) server that connects Claude — or any MCP-compatible AI assistant — to a live Pro Tools session via the PTSL (Pro Tools Scripting Library) API. Instead of navigating menus or writing scripts, you describe what you need in plain language and Claude handles it directly in your session.
Built for podcast post-production workflows, it works equally well across music production, broadcast, and audio post.
What It Looks Like in Practice
Once connected, you can have conversations like:
"What's in this session?" "Search the transcript for everywhere the guest mentions climate change." "Set a marker at 00:14:32:00 called 'Act Two'." "Mute all the music tracks and solo the host." "What clips are on the timeline between 22 and 35 minutes?" "Save a new version of this session called EP47_mix_v2." "Export the dialogue tracks as an AAF to the delivery folder."
Claude reads your live session state, answers questions about your timeline, and executes write operations directly in Pro Tools — no scripting, no keyboard shortcuts, no menu diving.
Capabilities
25+ tools across 7 functional groups:
| Group | Tools | Description |
|---|---|---|
| Session | get_session_info, get_markers, get_track_list, get_session_snapshot, get_show_profile | Session metadata, tracks, markers, show profiles |
| Tracks | get_track_edl, get_track_playlists, get_clips_in_range | Clip-level detail, playlists, time-range queries |
| Transcript | get_transcript, search_transcript, get_transcript_for_range | Speech-to-text CSV search with context and speaker labels |
| Navigation | get_playhead_position, get_current_selection, set_playhead | Playhead and selection state |
| Edit | select_region, create_marker, mute_track, unmute_track, solo_track, consolidate_clip | Session modifications (Claude confirms before executing) |
| Session Mgmt | save_session, close_session, open_session, save_session_as | Save, close, open, and version sessions |
| Export | export_tracks_as_aaf | AAF export with configurable format, bit depth, and copy option |
An optional Show Profile system lets you define per-show configuration — host names, track layouts, naming conventions — so Claude has the context it needs to work intelligently across multiple shows.
Prerequisites
- macOS with Pro Tools running (PTSL listens on
localhost:31416) - Python 3.11+ (tested with 3.11)
- py-ptsl installed system-wide or in a virtual environment
- Claude Desktop or Claude Code (for MCP integration)
- Accessibility permission for Claude/terminal (required for AAF export dialog automation)
Setup
-
Clone this repository:
git clone https://github.com/BlueElevatorProductions/protools-mcp.git cd protools-mcp -
Create a virtual environment:
python3 -m venv venv --system-site-packages source venv/bin/activate pip install -r requirements.txt --no-cache-dirThe
--system-site-packagesflag reuses your system-widepy-ptslandgrpcioinstalls. -
Configure
.env(optional — defaults shown):PTSL_HOST=localhost PTSL_PORT=31416 -
Add show profiles (optional): Place JSON files in
show_profiles/. Seeshow_profiles/holy_uncertain.jsonfor the format. -
Register with Claude Desktop — add to
~/Library/Application Support/Claude/claude_desktop_config.json:{ "mcpServers": { "protools-mcp": { "command": "/path/to/protools-mcp/venv/bin/python", "args": ["/path/to/protools-mcp/server.py"] } } }This makes the server available in Claude Desktop Chat, Cowork, and Code sessions.
For Claude Code CLI only, use:
claude mcp add protools-mcp -s user -- /path/to/protools-mcp/venv/bin/python /path/to/protools-mcp/server.py -
Grant Accessibility access (required for AAF export automation): System Settings > Privacy & Security > Accessibility — enable Claude Desktop and/or your terminal app.
-
Open Pro Tools with a session loaded. The MCP server connects lazily on first tool call.
Tool Reference
Session Context (read-only)
get_session_snapshot()— Composite: session info + markers + tracks + auto-matched show profile. Start here. Best tool to call at the beginning of any session conversation.get_session_info()— Session name, path, sample rate, bit depth, timecode format, track count, audio file count.get_markers()— All memory location markers with index, name, timecode, and comment.get_track_list(filter="all")— Tracks with active, muted, soloed, and hidden state. Filter:all,active,audio,inactive.get_show_profile(show_id?)— Returns show profile config. Auto-infers from session name prefix if no ID given.
Track Detail (read-only)
get_track_edl(track_name)— Full clip list for a track: clip name, start/end timecodes, duration, state.get_track_playlists(track_name)— All playlists on a track, including inactive alternates.get_clips_in_range(start_timecode, end_timecode, track_filter?)— All clips across tracks within a timecode range.
Transcript (read-only)
get_transcript()— Full transcript from a Pro Tools Speech-to-Text CSV export.search_transcript(query, track_filter?, start_timecode?, end_timecode?)— Keyword search with 2-row context window.get_transcript_for_range(start_timecode, end_timecode)— Transcript rows in a time range, formatted asSPEAKER: textdialogue.
Navigation
get_playhead_position()— Current playhead timecode.get_current_selection()— Start, end, duration, and selected track names.set_playhead(timecode)— Moves the playhead to a specified timecode.
Edit Operations (write)
All write tools are labeled [WRITE]. Claude will describe the operation and confirm before executing.
select_region(start_timecode, end_timecode, track_names?)— Sets timeline selection. Non-destructive.create_marker(name, timecode, comment?)— Adds a memory location marker at the specified timecode.mute_track(track_name)/unmute_track(track_name)— Toggles track mute state.solo_track(track_name)— Solos a track.consolidate_clip(track_name, start_timecode, end_timecode)— Consolidates a region into a single clip. Creates a new audio file on disk.
Session Management (write)
save_session()— Saves the current session to disk.save_session_as(session_name, session_location)— Saves with a new name.session_nameis the filename without extension;session_locationis the target directory.close_session(save_before_close=True)— Closes the session, optionally saving first.open_session(session_path)— Opens a.ptxor.ptfsession file.
Export (write)
export_tracks_as_aaf(...)— Exports selected tracks as an AAF. Handles the Pro Tools folder dialog automatically via osascript.audio_format:WAV(default),AIFF,MXF,Embeddedbit_depth:24(default),16copy_option:copy(default),consolidate,linkquantize_to_frame:true(default)avid_compatible:false(default) — enforce Media Composer compatibilitystereo_as_multichannel:false(default)sequence_name: defaults tofile_name
Transcript Support
The transcript tools expect a Pro Tools Speech-to-Text CSV export alongside the session. Place the CSV in your session directory (or set transcript_export_path in your show profile) and the server will discover it automatically. It reloads on file modification, so the data stays current as you iterate on transcripts.
Show Profile Format
Show profiles let Claude understand the structure of a specific show — which tracks belong to which speakers, naming conventions, and where exports live. Place JSON files in show_profiles/. Profiles are auto-matched by session name prefix.
{
"show_id": "HU",
"show_name": "Holy Uncertain",
"session_name_prefix": "HU-",
"hosts": ["Chris", "Lauren"],
"dialogue_tracks": ["Chris", "Lauren Int R", "Chris Int R"],
"guest_tracks": ["Randy Int R"],
"music_tracks": ["Music"],
"transcript_export_path": "/path/to/episodes/",
"naming_conventions": {
"session": "HU-{episode_number}-{guest_last_name}-V{version}",
"export": "HU-{episode_number}-{guest_last_name}-MIX-V{version}"
}
}
Architecture
Claude Desktop ──stdio──▶ server.py (FastMCP)
│
┌─────────────┼─────────────┐
▼ ▼ ▼
PTSLBridge Transcript ShowProfile
(gRPC) Watcher Loader
│ │ │
▼ ▼ ▼
Pro Tools CSV files JSON files
:31416
- PTSLBridge — Lazy gRPC connection with auto-reconnect. The
@ptsl_commanddecorator handles errors uniformly. CustomOperationsubclasses cover PTSL commands not in py-ptsl's ops module. - TranscriptWatcher — Stat-based CSV cache. Reloads only when the file's
mtimechanges. Auto-discovers CSV by searching the session directory. - ShowProfileLoader — Reads
show_profiles/*.jsononce at startup, matches sessions by name prefix. - osascript integration — For PTSL commands that trigger Pro Tools dialogs (e.g., AAF export), the bridge runs the command in a background thread and uses System Events to dismiss the dialog automatically. Requires Accessibility permission.
Error Handling
All PTSL errors return structured dicts before being raised as ToolError:
| Error Key | Meaning |
|---|---|
ptsl_unavailable | Pro Tools not running or gRPC connection lost |
no_session | No session is open in Pro Tools |
ptsl_command_error | PTSL command failed (details in message) |
no_transcript | No transcript CSV found or configured |
dialog_waiting | AAF export dialog needs manual confirmation (Accessibility not granted) |
Implementation Notes
- Timecode format: Pro Tools uses
HH:MM:SS:FF. Markers return raw sample positions internally; the bridge converts usingsamples_to_timecode(samples, sample_rate, fps). - Track
activefield: Derived fromis_inactive == TAState_NoneonTrackAttributes. Distinct from muted/hidden. - EDL text: Parsed from Pro Tools' tab-delimited text export with columns:
CHANNEL,EVENT,CLIP NAME,START TIME,END TIME,DURATION,STATE. - Pro Tools quirks:
SaveSessionAsand directory paths require a trailing/. Some commands (GetTrackPlaylists,GetPlaylistElements) needCId_-prefixed command IDs. Emptytrack_idfields must be stripped from JSON to avoid "only one of track_id/track_name" errors. - Connection management: gRPC connections can go stale between calls. The
@ptsl_commanddecorator catchesgrpc.RpcErrorand resets the connection automatically.
Troubleshooting
- "Pro Tools is not running" — Make sure Pro Tools is open with a session loaded. PTSL listens on port
31416. - Transcript not found — Set
transcript_export_pathin your show profile, or place the CSV next to the session file. - Stale data — EDL cache expires after 30 seconds. Transcripts reload on file modification. Call tools again for fresh data.
- AAF export hangs — Grant Accessibility access in System Settings > Privacy & Security > Accessibility for the app running the MCP server.
- "only one of track_id and track_name" — Handled internally by
json_messup()overrides on custom Operations.
Contributing
Issues and pull requests welcome. If you're using this in a specific workflow and run into edge cases, open an issue — Pro Tools has many quirks and real-world sessions surface them fast.
License
MIT
Built by Blue Elevator Productions
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.