Ableton for AI vs Speak AI
Ableton for AI is an MCP server published by peterkolbe. Marketplaces we read that list it: 1 (Official MCP Registry). Speak AI is an MCP server published by speakai. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (PyPI): 174 Downloads/week (PyPI): 27 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.39.1 Downloads/month (npm): 4 341 Downloads/week (npm): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.19.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.39.1 Downloads/month (npm): 4 341 Downloads/week (npm): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Ableton for AI | Speak AI |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | On your machine (ableton-for-ai) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/peterkolbe/ableton-for-ai | github.com/speakai/speakai-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 38 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Ableton for AI
Bridge between Ableton Live and AI. Inspect, analyze audio, and control mixing via MCP.
Speak AI
Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.
How to run each
Ableton for AI As a local MCP server: PyPI package
claude mcp add --transport stdio ableton-for-ai -- uvx ableton-for-ai
Speak AI As a remote MCP server
claude mcp add --transport http speak-ai https://api.speakai.co/v1/mcp
Requires: SPEAK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Speak AI has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Ableton for AI asks for
PREFERRED_AUDIO_FORMATSTEMS_SOURCE_DIR
Only Speak AI asks for
SPEAK_API_KEY (secret)SPEAK_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Ableton for AI · What it can do: Speak AI · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.