Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
talkback-mcpclaude mcp add talkback -e 'WS_PORT=<WS_PORT>' -- npx -y talkback-mcp@0.1.3{
"mcpServers": {
"talkback": {
"command": "npx",
"args": [
"-y",
"talkback-mcp@0.1.3"
],
"env": {
"WS_PORT": "<WS_PORT>"
}
}
}
}Environment variables
WS_PORTWebSocket port for the Max for Live bridge connection
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
talkback mcp
Chat with your Ableton session in natural language. Go deeper in your mix, make it sound like it does in your head, and finally understand compression... jk no one can teach you that.
Talkback is an MCP server and Max for Live device that gives AI assistants real-time access to your Ableton Live session — read tracks, adjust parameters, analyze your mix, and get spectral snapshots, all through conversation.
talkback.createwcare.com · Docs · Changelog
How it works
Ableton Live ↔ M4L Bridge ↔ WebSocket ↔ MCP Server ↔ Claude / Cursor / etc.- talkback bridge — a Max for Live device on your master track that reads the Live Object Model and streams session data over WebSocket
- talkback-mcp (this package) — an MCP server that exposes your session as tools any LLM can use
Quick start
The fastest way to get set up — installs the MCP server and configures Claude Desktop automatically:
curl -fsSL https://talkback.createwcare.com/install.sh | bashAlready in an AI agent? Let it set things up for you:
npx skills add jmedure/talkback-mcpThen ask your agent: "Help me set up talkback"
Requires Node.js 18+. See the full setup guide for more options.
1. Install the Max for Live device
Download talkback-bridge (latest) and drop it onto your master track in Ableton. Make sure the device is toggled on.
2. Add the MCP server
Talkback requires a desktop MCP client — it runs locally on your machine and connects to Ableton over WebSocket. It does not work with claude.ai in the browser (web chat doesn't support local MCP servers yet).
Claude Desktop (recommended)
Download Claude Desktop, then add to your config:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
%APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"talkback-mcp": {
"command": "npx",
"args": ["-y", "talkback-mcp"],
"env": { "WS_PORT": "8765" }
}
}
}Restart Claude Desktop after saving.
Using nvm or fnm? Claude Desktop doesn't load your shell profile, so it may pick up an old system Node. Use the full path to
npxinstead — runwhich npxin Terminal, then set that as"command"in the config above. See troubleshooting for details.
Claude Code
claude mcp add --transport stdio talkback-mcp -- npx -y talkback-mcpCursor
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"talkback-mcp": {
"command": "npx",
"args": ["-y", "talkback-mcp"],
"env": { "WS_PORT": "8765" }
}
}
}Other clients (Windsurf, etc.)
Point your client at npx -y talkback-mcp as the server command with WS_PORT=8765 as an environment variable.
Or use add-mcp to auto-configure all your installed agents:
npx add-mcp "npx -y talkback-mcp"3. Start chatting
Open your LLM and start asking about your session:
- "What's going on in my session?"
- "My bass sounds muddy, can you help?"
- "Cut 3 dB at 300 Hz on the vocal EQ"
- "Does my mix have any obvious problems?"
Your LLM will ask for approval before making any parameter changes. Undo always works.
Tools
| Tool | What it does |
|---|---|
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 |
Requirements
- Ableton Live 11+ with Max for Live
- Node.js 18+
- A desktop MCP client — Claude Desktop (recommended), Claude Code, Cursor, or similar
Environment variables
| Variable | Default | Description |
|---|---|---|
WS_PORT | 8765 | WebSocket port for bridge connection |
License
PolyForm Shield 1.0.0 — free to use, modify, and distribute. You may not use this software to build a competing product.
Frequently asked questions
What is io.github.jmedure/talkback?
Chat with your Ableton session in real-time.
How do I install io.github.jmedure/talkback?
It runs on your machine. In Claude Code: claude mcp add talkback -e 'WS_PORT=<WS_PORT>' -- npx -y talkback-mcp@0.1.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.jmedure/talkback need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.jmedure/talkback open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.jmedure/talkback?
It is published by jmedure. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.