Ableton MCP
Capped at 70: core tools not tested: no backing service on the test box; the tests add up to 90. Why scores are capped
Test points add up to 90; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (90/100)
- Install20/20
- Handshake30/30
- Maintenance15/25
- Docs15/15
- License10/10
Tested pypi ableton-mcp 1.4.5 (MIT; repo ahujasid/ableton-mcp). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 37 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. No passing real call: needs Ableton Live with its Remote Script running. Core tools not tested: 70 cap. Some error results include text addressed to the AI client asking it to prompt the user; we omit that text here.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. No passing real call: needs Ableton Live with its Remote Script running. Evidence: local test run, Nov 19, 2026 UTC.
Transport (tested 2026-11-19 UTC): stdio
Token cost (estimate): approx. 5348 tokens, cl100k estimate (37 tools, measured 2026-11-19 UTC, version 1.4.5). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 10 read, 19 write (state-changing), 8 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
add_notes_to_clip— write (state-changing)clear_notes_from_clip— write (state-changing)create_audio_clip— write (state-changing)create_audio_track— write (state-changing)create_clip— write (state-changing)create_locator— write (state-changing)create_midi_track— write (state-changing)delete_clip— write (state-changing)duplicate_to_arrangement— unclassifiedfire_clip— unclassifiedget_arrangement_clips— readget_browser_items_at_path— readget_browser_tree— readget_clip_notes— readget_device_parameters— readget_remote_script_info— readget_session_info— readget_session_snapshot— readget_track_info— readload_drum_kit— unclassifiedload_instrument_or_effect— unclassifiedprefer_candidate— unclassifiedrate_last_action— unclassifiedrecord_audition— unclassifiedreject_last_action— write (state-changing)set_arrangement_clip_name— write (state-changing)set_arrangement_time— write (state-changing)set_clip_name— write (state-changing)set_dataset_consent— write (state-changing)set_device_parameter— write (state-changing)set_tempo— write (state-changing)set_track_name— write (state-changing)start_playback— write (state-changing)stop_clip— write (state-changing)stop_playback— write (state-changing)submit_intent— unclassifiedswitch_to_arrangement_view— read
handshake and tools listed without a recorded key or OAuth
Score 70/100 · Tools 37 · Token cost approx. 5,348 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 1.4.5 · Package ableton-mcp · Repo ahujasid/ableton-mcp
Summary: Ableton MCP completed an MCP handshake without credentials and exposed 37 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 37
- Context cost
- approx. 5348 tokens, cl100k estimate (37 tools, measured 2026-11-19 UTC, version 1.4.5; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-19 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install ableton-mcp (Python venv, Linux) succeeded in 0s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 37 tools listed in 8.3s. |
| maintenance | partial | 15 | Repo pushed 57 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 5348 tokens, cl100k estimate for 37 tools · about 65% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-19 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 37 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
0575ff4f09fa: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "ableton-mcp",
"version": "1.4.5",
"registry": "pypi",
"status": "working",
"tested": "2026-11-19",
"tools_count": 37,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install ableton-mcp` (Python venv, Linux) succeeded in 0s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 37 tools listed in 8.3s."
],
"maintenance": [
"partial",
15,
"Repo pushed 57 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-19T06:10:01.595Z"
}Install
uvx ableton-mcp
Pin the version we tested
uvx ableton-mcp==1.4.5
pip install ableton-mcp==1.4.5
tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"ableton-mcp": {
"command": "uvx",
"args": [
"ableton-mcp==1.4.5"
]
}
}
}Tools listed
set_dataset_consent, get_session_info, get_remote_script_info, get_track_info, get_clip_notes, get_device_parameters, set_device_parameter, get_session_snapshot, create_midi_track, create_audio_track, set_track_name, create_clip, create_audio_clip, add_notes_to_clip, clear_notes_from_clip, set_clip_name, set_arrangement_clip_name, set_tempo, load_instrument_or_effect, fire_clip, stop_clip, delete_clip, start_playback, stop_playback, get_browser_tree, get_browser_items_at_path, load_drum_kit, switch_to_arrangement_view, set_arrangement_time, get_arrangement_clips, duplicate_to_arrangement, create_locator, submit_intent, rate_last_action, prefer_candidate, reject_last_action, record_audition
Quick config
{
"mcpServers": {
"ableton-mcp": {
"command": "uvx",
"args": [
"ableton-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install ableton-mcp(Python venv). This is the exact command we ran on 2026-11-19 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (37 in our test).
{
"mcpServers": {
"ableton-mcp": {
"command": "uvx",
"args": [
"ableton-mcp"
]
}
}
}Test history
- 2026-11-19 UTC: New
Related: Best dev MCP servers
FAQ
Is Ableton MCP deprecated?
No. Ableton MCP was not deprecated or archived when we last tested it on 2026-11-19 UTC.
What replaces Ableton MCP?
Nothing; Ableton MCP is not deprecated as of 2026-11-19 UTC.
Does Ableton MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 37 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.