§ Guide · For developers & agents

Pro Tools MCP server: what an agent can actually do

Q: How do I install it in Claude or Cursor?

In Claude Code, run claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp — the first tool call opens a browser for OAuth. In the Claude phone and web apps it installs as a custom connector with the same URL, and any MCP client can register it as a Streamable HTTP server, optionally sending an X-API-Key header instead of using OAuth.

Published September 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:

Realtime control of an open session. Avid's Pro Tools Scripting SDK (PTSL) is a language-independent API served over gRPC on localhost while Pro Tools is running: open, close and save sessions, query the session, run timeline operations, export, and get/set against what is loaded. py-ptsl is a Python binding, and community MCP servers wrap it. Nothing here replaces them. Note that the SDK is distributed to registered Avid developers, so a server built on it needs you to supply your own SDK.
Agent access to the project file. Converting a project, reading one, moving it to another DAW and back. That is a file-level problem: it works with Pro Tools closed, and on machines that do not have Pro Tools installed at all — a Linux box, a phone. It is what the Doseedo MCP server does.

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 line is for Claude Code; the first tool call opens a browser to sign in and approve. Headless clients append --header "X-API-Key: dsk_live_..." with a key from Settings → API keys. The same URL installs as a custom connector in the Claude phone and web apps, and in Cursor or any MCP client as a Streamable HTTP server. Nothing to self-host, and no Avid developer registration involved; the full tool list is on the MCP server page.

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:

Convert, natively. Eight directions — .ptx to and from Logic Pro, Ableton Live, FL Studio and REAPER — rebuilt in the target format rather than exported through an interchange file, so tracks, MIDI, audio clips, tempo and markers arrive editable.
Read a project. An agent can answer "what is in here, and is the media complete?" with Pro Tools closed. Opening a .ptx without Pro Tools covers the manual route, and what is a .ptx file covers the format.
Bridge a room that is not on Pro Tools. The common case is a handoff — writing in Ableton or FL, mixing in Pro Tools — and the conversion goes both ways, so the session can come back.

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

Your audio does not necessarily leave the machine

For files already on your disk, the agent passes the local path: the cloud builds the session structure — tracks, regions, buses, routing — and the download hands back copy commands that place your own files into the project. Audio uploads only when the server needs the samples: separation, transcription, conversion, generation or a bounce.

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

No live control of an open Pro Tools session. No transport, no timeline operations, no reading the loaded session. That is Avid's Scripting SDK, py-ptsl, and the MCP servers built on them.
No one-shot session download as .ptx. Saving a Doseedo session directly to a native file targets Logic, Ableton, FL Studio and REAPER; Pro Tools is reached by converting from one of those. It is a real extra step and we would rather name it than have a tool call fail on you.
Session building does not target Pro Tools directly. A mix becomes a Logic or Ableton session first, then converts.
Live session editing targets Logic Pro today, through the Doseedo Desktop bridge on macOS.
Offline bounce is Logic-side too — printing tracks through their real plugin chains with the DAW closed runs through that same bridge.
Plugin state and automation have limits off the direct Logic↔Ableton path. Move arrangements and media this way, not finished mixes.

Why Pro Tools is a file surface here and Logic is a live one

Because the gaps are in different places. Logic ships no public realtime scripting surface — Scripter is JavaScript confined to one channel strip — so reaching an open Logic project takes a native bridge, 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

Drive a session that is open right now: Avid's Pro Tools Scripting SDK, py-ptsl, or an MCP server built on them.
Move a project between Pro Tools and another DAW, in either direction: the MCP server.
Read or check a .ptx on a machine without Pro Tools: the MCP server.
Have an agent edit an open project as you watch: Logic Pro, with Doseedo Desktop running.

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 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.

Which DAW gets live session editing today?

Logic Pro, on macOS, through the Doseedo Desktop bridge. With the desktop app running and the project open, agent edits — moving regions, rewriting MIDI, faders, plugins, tempo — land in the open Logic project within seconds. Pro Tools is not driven live by this server; for Pro Tools the surface is the project file.

How do I install it in Claude or Cursor?

In Claude Code, run claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp — the first tool call opens a browser for OAuth. In the Claude phone and web apps it installs as a custom connector with the same URL, and any MCP client can register it as a Streamable HTTP server, optionally sending an X-API-Key header instead of using OAuth.