Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Chat with your Ableton session in real-time.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
WS_PORTYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"talkback": {
"command": "npx",
"args": [
"-y",
"talkback-mcp"
],
"env": {
"WS_PORT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add talkback --env WS_PORT=your-value -- npx -y talkback-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"talkback": {
"command": "npx",
"args": [
"-y",
"talkback-mcp"
],
"env": {
"WS_PORT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"talkback": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"talkback-mcp"
],
"env": {
"WS_PORT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
WS_PORT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account jmedure, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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](https://talkback.createwcare.com) · [Docs](https://talkback.createwcare.com/docs/getting-started) · [Changelog](https://talkback.createwcare.com/docs/changelog)
Ableton Live ↔ M4L Bridge ↔ WebSocket ↔ MCP Server ↔ Claude / Cursor / etc.
The fastest way to get set up — installs the MCP server and configures Claude Desktop automatically:
curl -fsSL https://talkback.createwcare.com/install.sh | bash
Already in an AI agent? Let it set things up for you:
npx skills add jmedure/talkback-mcp
Then ask your agent: *"Help me set up talkback"*
Requires Node.js 18+. See the full setup guide for more options.
Download talkback-bridge (latest) and drop it onto your master track in Ableton. Make sure the device is toggled on.
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-mcp
Cursor
Add to .cursor/mcp.json in your project root:
{
"mcpServers": { "talkback-mcp": { "command": "npx", "args": ["-y", "talkback-mcp"], "env": { "WS_PORT": "8765" } } } }
</details>
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"
Open your LLM and start asking about your session:
Your LLM will ask for approval before making any parameter changes. Undo always works.
| 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 |
| Variable | Default | Description |
|---|---|---|
WS_PORT | 8765 | WebSocket port for bridge connection |
PolyForm Shield 1.0.0 — free to use, modify, and distribute. You may not use this software to build a competing product.