§ Guide · For developers & agents

Pro Tools MCP server: what an agent can actually do

Published September 2026 · Updated October 2026

Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that lets an AI agent convert and read Pro Tools projects: move a .ptx to or from Logic Pro, Ableton Live, FL Studio and REAPER, and read what is inside one with Pro Tools closed. What it does not do is drive the session open on your screen right now. Avid ships an official Scripting SDK for that, and there are already MCP servers built on it; this page will point you at them rather than blur the line.

Two different things called "Pro Tools MCP"

Pro Tools is the one DAW where both halves genuinely exist, from different people, and confusing them is how people end up disappointed:

The two do not compete. PTSL never opens a .ptx that is not loaded; a file-level tool never sees your playhead. Use both: move the project with one, run the session with the other.

Setup

claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp

That is the Claude Code form; the first tool call opens a browser to sign in, and a client without a browser sends X-API-Key: dsk_live_… from Settings → API keys. No Avid developer registration is involved at any point; that is the realtime SDK's requirement, not this one. The same URL goes into ChatGPT, Cursor, Gemini CLI, Codex and VS Code; the reference lists all 33 tools.

The seventeen directions doseedo_convert_project accepts for a .ptx, from the tool's own enum: protools2logic logic2protools protools2ableton ableton2protools protools2fl fl2protools protools2reaper reaper2protools protools2cubase cubase2protools protools2dorico dorico2protools garageband2protools protools2bitwig bitwig2protools protools2studioone studioone2protools, plus auto2protools to detect the source.

What the agent can do with a Pro Tools project

You talk to it in project terms; it handles uploads, polling and downloads itself:

> Convert this Pro Tools session to Logic, and tell me what
  won't survive the trip.

> The band works in Ableton and the mix room is Pro Tools.
  Take this .als to .ptx so I can hand it over.

> What's in this .ptx? List the tracks and every audio file
  it references, so I can check the media is all here.

Concretely, the capabilities that apply to Pro Tools:

Long jobs are async: the submit tool returns a task_id and a wait tool polls it until the artifact is ready.

Send the session folder, not the .ptx

A Pro Tools session is a folder (the .ptx beside Audio Files, Session File Backups and the rest), and the .ptx on its own references media it does not contain. Compress the whole folder for a conversion, the way you would for a handoff, and the agent can check the media is complete before it converts: it reads the session and lists every referenced file, which is also the quickest answer to "is everything here?" on a drive that arrived from another studio. Audio uploads only for jobs that read it; a session built from files on your disk references them by path.

Install it and try one conversion

Add the server, point your agent at a Pro Tools session, and ask it to convert, and to tell you what it had to leave behind.

The Doseedo MCP server →

What it does not do: read this before you install

Why Pro Tools is a file surface here and Logic has a bridge

Because the gaps are in different places. Logic ships no public realtime scripting surface (Scripter is JavaScript confined to one channel strip), so reaching a Logic project takes a native app that saves it, closes it, writes the edits in and reopens it, which is what the desktop app is (the Logic side, in detail). Pro Tools already has a supported, documented realtime API in PTSL, and people have built on it. What Pro Tools does not have is a way to get a session out of Pro Tools and into another DAW with the arrangement intact, or back again: that is the part this fills.

Which tool for which job

FAQ

Is there an MCP server for Pro Tools?

There are two kinds. Avid ships an official Pro Tools Scripting SDK (PTSL), and community MCP servers use it to drive a session that is open right now. Doseedo runs a different one, hosted at api.doseedo.com/mcp, that works on the project file: converting a .ptx to or from Logic Pro, Ableton Live, FL Studio and REAPER, with Pro Tools closed and on machines that do not have it installed.

Can Claude or ChatGPT control Pro Tools in realtime?

Not through this server. Avid's Scripting SDK exposes a gRPC interface on localhost while Pro Tools is running (open, close and save sessions, query the open session, drive the timeline, export), and py-ptsl plus community MCP servers wrap it. That is the realtime route, and it is a genuinely different surface from project files.

What can an AI agent do with a .ptx file?

Convert it to or from Logic Pro, Ableton Live, FL Studio and REAPER, eight directions, rebuilt natively so tracks, MIDI, audio clips, tempo and markers arrive editable. Reading a .ptx to answer what is inside it is covered too.

Can it download a session as a Pro Tools project?

Not as a one-shot download today. Saving a Doseedo session straight to a native file targets Logic Pro, Ableton Live, FL Studio and REAPER; the Pro Tools route is conversion: build or edit the session, save it to one of those, and convert to .ptx. We would rather say that plainly than have the tool fail on you.

Do I need Pro Tools, or Avid's SDK, installed where the agent runs?

No. Conversion and reading happen on the server, so the agent can run anywhere: a phone, a Linux box, a Mac without Pro Tools. The Scripting SDK (PTSL) is what the realtime servers need, and it comes with Avid developer registration; this does not use it. Writing edits into a project on your Mac is Logic Pro only, through the macOS desktop bridge.

Can it save a session straight to .ptx?

Not in one call. download_session writes a native Logic project; Pro Tools is reached by converting that (logic2protools), which the agent does for you as a second call. The honest cost is one extra credit and a minute, not a missing capability.

The Doseedo MCP server · one URL, every client

By DAW
By AI client
By capability

Related