Skip to content

MCP server

Wisdom Pro speaks the Model Context Protocol (MCP) over stdio, so Claude and other AI agents can make music with it. An agent can run Wisdom Pro headless, with no window and no audio device, or connect to the desktop app you have open, where it can also take screenshots and click.

Terminal window
wisdom-cli mcp # headless engine (no window, no audio device)
wisdom-cli mcp --demo # headless, starting from the demo session
wisdom-cli mcp --automation-read-root DIR --automation-write-root DIR # headless, confined to folders
wisdom --control 7801 & # the desktop app…
wisdom-cli mcp --connect 7801 # …driven over MCP: same tools plus screenshots and clicks
Terminal window
claude mcp add wisdom -- wisdom-cli mcp --demo
claude mcp add wisdom -- wisdom-cli mcp --connect 7801 # the running app

Two flags keep the agent to the folders you give it:

Terminal window
wisdom-cli mcp --automation-read-root /work/project --automation-write-root /work/project/out

The same setting in an MCP client’s config file:

{"mcpServers": {"wisdom": {"command": "wisdom-cli",
"args": ["mcp", "--automation-read-root", "/work/project", "--automation-write-root", "/work/project/out"]}}}
  • Every file a command reads, such as a session it opens, audio it imports or a preset it loads, must lie inside the read root.
  • Every file a command writes, such as a save, a bounce or an export, must lie inside the write root. What an agent may write, it may also read back.
  • With only --automation-read-root, nothing can be written to disk. With only --automation-write-root, nothing outside it can be read. Without either flag nothing changes.
  • A refused path is an ordinary tool error the agent can read and correct.
  • The roots must be existing folders; a missing one stops the server with an error.

For a Wisdom Pro project, give the song folder as both roots:

Terminal window
wisdom-cli mcp --automation-read-root "$HOME/Music/Wisdom Pro/<Song>" \
--automation-write-root "$HOME/Music/Wisdom Pro/<Song>"

The flags confine the headless server only. Using them together with --connect is an error, and a running app (wisdom --control) is not confined.

Tool Purpose
list_commands Discover every command (id, label, menu path, shortcut, params, enabled).
execute Run one command with JSON params.
batch Run up to 1000 commands in order.
inspect_session Check the work: tracks, clips, mixer, plug-ins, sends, automation, markers, selection.
new_session, open_session, save_session Session files.
import_audio WAV, AIFF, FLAC, MP3, OGG, AAC/M4A, ALAC, CAF onto a new or existing track.
bounce_mix Render the song; returns peak dBFS and integrated LUFS.
screenshot, ui_inspect, ui_set, menu_invoke, click, drag, key Only when connected to the app (--connect).

Programmatic calls never open dialogs, and every command is undoable unless it is a query or a view setting.

Built so far:1,292 hours24.1 billion tokensabout $8,700 at API pricesupdated Nov 21, 2026 What these numbers mean