Control Ableton Live from Claude, Cursor or Codex with LOM tools, device knowledge and recipes.
Most cloud and infrastructure work still happens through a UI a human drives. Ableton MCP server moves it into the conversation instead. Control Ableton Live from Claude, Cursor or Codex with LOM tools, device knowledge and recipes.
Definitive MCP (Model Context Protocol) server for Ableton Live. Exposes the full Live Object Model to LLMs (Claude, Cursor, etc.) with an embedded native device knowledge base, declarative music recipes, an integrated verify loop, and reactive listeners.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 14 tools. What each one is for:
macOS — ** copy live/AbletonMind/ to ~/Music/Ableton/User Library/Remote Scripts/AbletonMind/Windows — ** copy to ~/Documents/Ableton/User Library/Remote Scripts/AbletonMind/Glama — ** listed at glama.ai/mcp/servers/Pantani/ableton-mind; hosted release is separate from theSource — ** npm ci && npm run build && npm run install:remote-scriptSmithery — ** smithery.yaml is ready for listing/indexingCapability — ahujasid/ableton-mcpRecipes — noneVar — DefaultABLETON_MIND_HOST — 127.0.0.1ABLETON_MIND_PORT — 9876ABLETON_MIND_TIMEOUT_MS — 5000ABLETON_MIND_MAX_FRAME_BYTES — 1048576Configuration is passed through the environment: ABLETON_MIND_HOST, ABLETON_MIND_LLM_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ableton's toolset — macOS, Windows, Glama and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Pantani; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ableton's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| macOS | ** copy live/AbletonMind/ to ~/Music/Ableton/User Library/Remote Scripts/AbletonMind/ |
| Windows | ** copy to ~/Documents/Ableton/User Library/Remote Scripts/AbletonMind/ |
| Glama | ** listed at [glama.ai/mcp/servers/Pantani/ableton-mind](https://glama.ai/mcp/servers/Pantani/ableton-mind); hosted release is separate from the GitHub Release and still requires the Glama admin deploy + Make Release flo |
| Source | ** npm ci && npm run build && npm run install:remote-script. |
| Smithery | ** [smithery.yaml](smithery.yaml) is ready for listing/indexing. |
| Capability | ahujasid/ableton-mcp |
| Recipes | none |
| Var | Default |
| ABLETON_MIND_HOST | 127.0.0.1 |
| ABLETON_MIND_PORT | 9876 |
| ABLETON_MIND_TIMEOUT_MS | 5000 |
| ABLETON_MIND_MAX_FRAME_BYTES | 1048576 |
| ABLETON_MIND_MAX_PENDING_REQUESTS | 128 |
| ABLETON_MIND_LOG_LEVEL | info |
{
"mcpServers": {
"ableton-mind": {
"command": "npx",
"args": ["-y", "ableton-mind-doctor"],
"env": {
"ABLETON_MIND_HOST": "your-value",
"ABLETON_MIND_LLM_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ABLETON_MIND_HOST | Endpoint or connection string the server talks to. | Optional |
| ABLETON_MIND_LLM_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.