Log inSubmit server
Talkback logo

Talkback

Connects AI assistants to Ableton Live for session inspection, mix analysis, spectral snapshots, and controlled track or device changes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Talkback

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "talkback": {
      "command": "npx",
      "args": [
        "-y",
        "talkback-mcp"
      ],
      "env": {
        "WS_PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y talkback-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

The talkback MCP server connects AI assistants to Ableton Live through a Max for Live bridge and WebSocket connection. It exposes tools for reading session state, inspecting devices, analyzing mixes, capturing master-bus spectral data, and changing selected parameters or routing. Use it when you want conversational access to a local Ableton session through a desktop MCP client. It requires Ableton Live 11 or newer with Max for Live, Node.js 18+, and the talkback bridge device installed on the master track.

Use cases

  • Inspect an Ableton session through natural-language questions
  • Analyze a mix for frequency, dynamics, headroom, and routing issues
  • Adjust device parameters using dB, ms, or Hz values
  • Compare a device with bypass toggles
  • Create groups and change track routing

Key features

  • Ableton Live session inspection
  • Track and device detail queries
  • Master-bus spectral snapshots
  • Heuristic mix analysis
  • Device parameter and bypass control
  • Track grouping and routing changes

Tools10

What Talkback lets your agent do. Expand a tool for its parameters.

Self-reported~208 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 18h ago via OSV.dev · talkback-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars25Stargazers on the source repository.
npm downloads174Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed10Callable tools this server registers over MCP.

How Talkback works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Talkback

talkback is an MCP server that connects AI assistants to Ableton Live through a Max for Live bridge and WebSocket. Its main tools read session and track details, capture spectral snapshots, analyze mixes, list plugins, change device parameters, toggle bypass, create groups, and update track routing.

Install it with `npx -y talkback-mcp`, then install the talkback-bridge Max for Live device on Ableton’s master track. Node.js 18 or newer is required. The provided installation script can configure Claude Desktop automatically, or you can add the server manually to a desktop MCP client.

Yes, talkback works with Cursor through its project-level `.cursor/mcp.json` configuration. Point Cursor to `npx -y talkback-mcp` and set `WS_PORT` to `8765`, unless the bridge is configured to use another port.

Yes, talkback can change device parameters with `set_device_parameter`, using human-readable units such as dB, milliseconds, and hertz. It can also toggle device bypass, change track routing, and create group tracks.

No, talkback does not work with Claude’s browser-based web chat because web chat does not support local MCP servers. Use a desktop MCP client such as Claude Desktop, Claude Code, Cursor, or another client that can run the server locally.

Related MCP servers

All in Multimedia Process All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTalkback AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/talkback?style=directory)](https://allmcps.com/mcp/talkback)
HTML Embed
<a href="https://allmcps.com/mcp/talkback"><img src="https://allmcps.com/api/badge/talkback?style=directory" alt="Talkback on AllMCPs" /></a>