§ Reference · Model Context Protocol

The 33 tools, what each one does

Published October 2026

This is the tool table of the Doseedo MCP server at https://api.doseedo.com/mcp, in prose: 33 tools in five families. Session control reads and edits a DAW session (live in Logic Pro with Dø Desktop). Projects imports, converts and builds whole project files across ten DAW formats. Audio and music generates, separates and transcribes. Analysis answers key, tempo and chord questions synchronously and for free. The last family is plumbing: uploads, waiting, cost. The machine-readable version is the server card, built from the same array the protocol serves.

How the tools fit together

Three tools work before you have signed in — doseedo_recipes, doseedo_edit_ops_reference and doseedo_quote — because they read no account and spend nothing; an agent reads the recipes and the op catalog first, then authenticates on its first real call. Ids are stable: tracks are t_…, their mixer strips ch_…, and everything else (parameters, markers, clips) comes from a session read. Beats are absolute from bar 1; a fader at 0.709 is 0 dB. Every long job returns a job_id and is waited on with doseedo_wait_task; every result is a pre-signed link that works for 24 hours with a plain curl, and can be handed to the next tool as its input.

Keys carry scopes: a full key, a read-only key (read:sessions — writes answer 403 and the agent is told which scope it needs), and ops:<group> keys that allow one category of edit — mixer, regions, plugins, tracks, project, markers, automation, history. Mint them at Settings → API keys; OAuth grants appear there too.

Session control — read and edit a DAW session

The family that makes "control my DAW" literal. Every edit lands in the cloud session; with Dø Desktop running it is applied to the open Logic project within seconds.

ToolWhat it does
doseedo_list_sessionsThe sessions in the connected account — ids, names, DAW, last update — newest first, paged with limit and offset.
doseedo_create_sessionA new, empty session: a blank project the agent then populates with edits, or targets with a build.
doseedo_get_sessionOne session as an arrangement an agent can reason about: every track with its ids, regions in beats and seconds, mixer levels in dB, plugin chains with parameter ids, tempo, time signature, markers, the key when it is known — and sync.live_edits, the one answer to "will my change land live?". Notes are omitted on a large session unless asked for.
doseedo_edit_sessionA list of ops applied in one atomic call (up to 500): move and trim regions, rewrite MIDI notes, add and delete tracks, faders, pan, mute, insert plugins by name, set parameters, tempo, key, markers, submix buses and routing, Quick Sampler samples. A rejection names the op, a code and a did_you_mean; a batch_key makes a retry dedup.
doseedo_edit_ops_referenceThe catalog of ops edit_session accepts — units, ids, recipes — served in views that each fit one answer. Open: no credential needed.
doseedo_download_sessionThe session as a native .logicx, rebuilt server-side from the edit log, no desktop needed. Returns a no-auth link plus a replay report of what landed, and the copy commands that place local files back into the project.
doseedo_bounce_sessionPrint tracks (or the whole session) to WAV or AIFF through their real plugin chains, offline — Dø Desktop renders in the background without opening the DAW for you.
doseedo_add_audio_to_sessionPut an audio file onto a session — a generated take, a separated stem, any https URL, or a file you uploaded — ready to place on a track.
doseedo_list_pluginsThe plugins an agent may insert by name: the stock Logic catalog always, plus the instruments and effects installed on your Mac while the desktop is connected.
doseedo_desktop_statusIs Dø Desktop running and connected to Logic, which sessions it holds, whether edits will land live — read-only.
doseedo_delete_sessionsSoft-delete sessions in bulk, with a dry run first; nothing on your disk is touched.

Projects — import, convert, build

The file-level half: whole projects in and out, across ten DAW formats.

ToolWhat it does
doseedo_get_project_upload_urlA presigned upload for a project zip (zip the folder so the audio travels with it); multipart past 4 GB.
doseedo_complete_project_uploadFinishes a multipart project upload from the part ETags.
doseedo_import_projectOpens an uploaded Logic, Ableton, FL Studio, REAPER or Pro Tools project as an editable session — the way into edit_session for a project that already exists.
doseedo_convert_projectConverts a project between Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER, Cubase, Dorico, Studio One and Bitwig, with GarageBand in — 75 directions, rebuilt natively so tracks, MIDI, audio, tempo and markers arrive editable. auto2<target> detects the source; an option drops third-party plugins for a machine that lacks them.
doseedo_audio_to_sessionA full mix in, a native Logic or Ableton session out: separated stems on named tracks, a tempo map, section markers, optional per-stem MIDI and a chord guide. About four minutes.

Audio and music — generate, separate, transcribe

The AI-audio tools behind the site, on the same connection.

ToolWhat it does
doseedo_generate_musicAn original song or instrumental from a text prompt, with optional lyrics and a target length. Tempo and meter are caption hints, not controls — a part that must fit a session is written as notes and rendered instead.
doseedo_render_midiYour exact notes, played by a modelled instrument at your tempo: notes in beats, a MIDI file, or a session track; up to four takes per call, a timbre preset or a short recording whose sound the render takes on, and a voice split for chords.
doseedo_cover_songRe-render an uploaded song keeping its structure: swap instruments per stem, change the genre, replace the lyrics, optionally take the timbre of a reference mix.
doseedo_separate_stemsA mix into vocals, drums, bass, guitar, piano and other — or an orchestral / auto-detected instrument set — with optional per-stem MIDI, a drum split into kick, snare, hats, toms and cymbals, a guitar split into players, and an optional session built from the result.
doseedo_transcribeAudio to notes (pitch, onset, offset, velocity, confidence) with instrument, register and polyphony hints — including a horn section by chairs — and optionally the continuous pitch contour.

Analysis — synchronous, no credits

Answers in one call and costs nothing; the grid an agent writes a part against.

ToolWhat it does
doseedo_analyze_songKey, bpm and per-beat tempo map, meter, downbeats, sections, chords of a recording.
doseedo_detect_chordsA chord chart with spans in seconds and beats.
doseedo_beat_gridBeat and downbeat times, beats per bar, the beat map.
doseedo_analyze_midiThe harmony of notes you wrote, before rendering or placing them.

Files, jobs and the account

The plumbing: uploads, waiting, cost.

ToolWhat it does
doseedo_get_upload_urlA presigned upload for your own audio (WAV, AIFF, FLAC, MP3, M4A, Ogg); returns the audio_key every processing tool takes.
doseedo_wait_taskWaits on an async job server-side, up to 50 seconds per call, and returns the result when it is done.
doseedo_check_taskOne status check, and fresh download links for a finished job whose links expired.
doseedo_list_jobsThe account's jobs, newest first, filtered by kind, status or session.
doseedo_cancel_jobStops a queued or running job; what is refunded depends on the kind.
doseedo_quoteThe credit cost of a job before submitting it, and whether the account can afford it now. Open: no credential needed.
doseedo_recipesThe named pipelines — stems, session, cover, transcribe, generate, render-midi, analyze-song, convert, import-edit-export, bounce — with inputs, the calls in order, and how to verify. Open: no credential needed.
doseedo_accountPlan tier, the monthly credit pool, purchased extra usage, storage — read-only.

What a response looks like

Every tool answers in JSON that reads as prose when an agent relays it. This is a real doseedo_quote reply, captured 2026-10-15, for a 21-second upright-bass render with three takes — note that the three takes are free, that the rule is spelled out in basis, and that affordable is answered against the connected account:

{
  "job": "render_midi",
  "route": "/api/generate-stemphonic",
  "estimate": { "generation": 10 },
  "basis": "10 credits per 30 s window (21 s → 1 window) → 10 credits",
  "assumptions": [
    "takes (3) render in one GPU batch and cost nothing extra",
    "a chord part split into voices (voice_split) costs one batch per ~6 voices — pass voices to price it",
    "estimate only — the plane gate is authoritative and a refusal names the exact price",
    "failed jobs are refunded; free accounts also have a monthly ceiling"
  ],
  "account": { "tier": "…", "remaining": { "generation": "…" }, "resets_at": "2026-10-16T00:00:00+00:00" },
  "affordable": true
}

Errors have one shape too — {error, code, retryable, plane, next, request_id} — and next is an instruction the agent follows: when the analysis service did not answer within 45 seconds during this page's own capture, the reply said "Wait 30 s and retry ONCE; do not loop", the retry succeeded, and the request_id is what support asks for. A result too large for one answer comes back reshaped rather than cut: a truncated list says which arrays were shortened and next says how to fetch the rest.

Recipes: the named pipelines

doseedo_recipes returns ten pipelines an agent follows call by call — stems, session (a mix into a DAW project), cover, transcribe, generate, render-midi (your notes played by an instrument), analyze-song, convert, import-edit-export (open a project, edit it, hand it back) and bounce — each with its inputs, the tools in order, what it costs and how long it takes, and how to verify the result from the response rather than by unzipping it. The same recipes ship as the skills pack (npx skills add doseedo/skills) for Claude Code, Cursor, Codex and the other agents that read skills.

Connect it

One URL, every client. The install for each — Claude, ChatGPT, Cursor, Gemini CLI, Codex, VS Code — is one page away.

The Doseedo MCP server →

FAQ

How many tools does the Doseedo MCP server have?

33, in five families: session control (read, edit, download, bounce), projects (import, convert, build from audio), audio and music (generate, render MIDI, cover, separate, transcribe), analysis (key, tempo, chords, beat grid, MIDI harmony — synchronous and free), and jobs and account (uploads, wait, list, cancel, quote, recipes).

Which tools work without signing in?

doseedo_recipes, doseedo_edit_ops_reference and doseedo_quote. They answer from constants or the public op catalog and spend nothing. Every other tool needs an OAuth sign-in or an X-API-Key header.

Which tools are free?

The analysis tools — analyze_song, detect_chords, beat_grid, analyze_midi — run synchronously and cost no credits, as do reads, quotes, listings and the reference tools. Generation, rendering, covers, separation, transcription, session builds, conversions and bounces draw on the account's credit pool; quote prices them first.

Do I get a MIDI file from doseedo_transcribe?

It returns notes as JSON — pitch, onset and offset in seconds (and beats when a tempo is given), velocity, confidence. Separation with include_midi, and audio_to_session, write MIDI into the project; render_midi accepts a Standard MIDI File URL as input.

Where is the machine-readable tool list?

At api.doseedo.com/.well-known/mcp/server-card.json — identity, auth shape and the full tool table, built from the same array the protocol serves. An anonymous tools/list on the endpoint returns the same.

The Doseedo MCP server · one URL, every client

By DAW
By AI client
By capability

Related