# talkback [Health: Active]

**Category:** 🎥 Multimedia Process  
**Repository:** https://github.com/jmedure/talkback-mcp  
**GitHub Stars:** 25  
**npm Downloads (last month):** 168  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/talkback

## Description
Chat with your Ableton session in real-time.

## Tools
Capabilities this server exposes over MCP:

- **get_session_context** — Reads your full session — tracks, volumes, panning, mutes, sends, devices, routing
- **get_track_details** — Deep-dives a single track with every device parameter in human-readable units
- **get_spectral_snapshot** — Captures ~2s of live audio from master bus with peak/RMS per frequency band
- **get_plugin_library** — Lists all installed AU and VST3 plugins on your system
- **analyze_mix** — Runs heuristic checks for frequency buildup, dynamics, headroom, and routing issues
- **set_device_parameter** — Changes a device parameter using human-readable units (dB, ms, Hz, etc.)
- **toggle_device_bypass** — Enables or bypasses a device for A/B comparison
- **create_group_track** — Creates a new group track containing specified tracks
- **set_track_routing** — Changes a track's output routing to another track or bus
- **get_bridge_health** — Returns bridge performance metrics from the M4L device

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "talkback": {
    "command": "npx",
    "args": ["-y","talkback-mcp"],
    "env": {
      "WS_PORT": ""
    }
  }
}
```

**Requires environment variables:** `WS_PORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What talkback MCP server does

The talkback MCP server gives an AI assistant structured access to an Ableton Live session. It can read tracks, levels, panning, mutes, sends, devices, and routing, then return that information in a form the assistant can discuss. It also supports selected edits, including device parameter changes, bypass toggles, group-track creation, and track-output routing.

The server is intended for conversational session work rather than general-purpose audio production control. You can ask about the current arrangement, inspect an individual track, investigate mix problems, or request a specific adjustment. Parameter values use familiar units such as decibels, milliseconds, and hertz where supported.

## How it works

A Max for Live device called talkback-bridge runs on the Ableton master track. The bridge reads Ableton’s Live Object Model and sends session information over WebSocket. The talkback MCP server listens for that connection and presents the session operations as MCP tools to a compatible local client.

The connection path is:

- Ableton Live and the Max for Live bridge
- WebSocket connection
- MCP server
- Desktop AI client

The bridge also provides health information through `get_bridge_health`, including performance metrics reported by the device.

## Setup and configuration

Install the talkback-bridge device and place it on the master track in Ableton Live, then make sure it is enabled. Install Node.js 18 or newer. The server can be installed with `npx -y talkback-mcp`, or the provided installation script can configure Claude Desktop automatically.

For a manual client configuration, run the server with `npx` and set `WS_PORT` to the port used by the bridge. The documented default is `8765`. Claude Desktop uses a JSON MCP configuration, while Claude Code can add the server with its `claude mcp add` command. Cursor uses a project-level `.cursor/mcp.json` file. Other desktop clients can be pointed at the same command and port setting.

## Tools and capabilities

The talkback MCP server exposes these operations:

- `get_session_context` reads the complete session state.
- `get_track_details` reports device parameters for one track in human-readable units.
- `get_spectral_snapshot` samples roughly two seconds of master-bus audio and reports peak and RMS values by frequency band.
- `get_plugin_library` lists installed AU and VST3 plugins.
- `analyze_mix` checks for possible frequency buildup, dynamics, headroom, and routing problems using heuristics.
- `set_device_parameter` changes a device parameter.
- `toggle_device_bypass` enables or bypasses a device for comparison.
- `create_group_track` creates a group containing specified tracks.
- `set_track_routing` changes a track’s output destination.
- `get_bridge_health` returns bridge performance metrics.

## Limitations and notes

The talkback MCP server requires a local desktop MCP client and does not work with Claude’s browser-based web chat, because that environment does not support local MCP servers. It also depends on Ableton Live 11 or later with Max for Live and an active bridge device on the master track.

AI assistants request approval before making parameter changes, and Ableton’s undo behavior remains available. Mix analysis is heuristic, so its findings should be treated as checks to investigate rather than definitive engineering conclusions. The software is licensed under PolyForm Shield 1.0.0, which permits use, modification, and distribution but restricts building a competing product.

_Full upstream README: https://allmcps.com/mcp/talkback/readme_