Ableton Mcp Suite MCP Server

ableton-mcp-suite PyPI v1.0.0

Published by farmhutsoftwareteam — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Heavily extended Ableton Live integration via MCP — 45 tools (vs 16 upstream) for device parameters, sidechain routing, arrangement view, return/master tracks, audio import, and clip editing from Claude

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 45

Each tool and what it can reach — statically extracted from the published source.

  • add_notes_to_clipno sensitive capability
  • clear_arrangement_clipsno sensitive capability
  • clear_locatorsno sensitive capability
  • create_audio_trackno sensitive capability
  • create_clipno sensitive capability
  • create_midi_trackno sensitive capability
  • delete_arrangement_clipno sensitive capability
  • delete_clipno sensitive capability
  • delete_deviceno sensitive capability
  • delete_trackno sensitive capability
Show 35 more tools ↓
  • fire_clipno sensitive capability
  • get_arrangement_clipsno sensitive capability
  • get_browser_items_at_pathno sensitive capability
  • get_browser_treeno sensitive capability
  • get_device_parametersno sensitive capability
  • get_device_routingsno sensitive capability
  • get_master_track_infono sensitive capability
  • get_session_infono sensitive capability
  • get_track_infono sensitive capability
  • import_audio_fileno sensitive capability
  • load_drum_kitno sensitive capability
  • load_instrument_or_effectno sensitive capability
  • mute_arrangement_clipno sensitive capability
  • place_audio_in_arrangementno sensitive capability
  • place_clip_in_arrangementno sensitive capability
  • set_arrangement_clip_gainno sensitive capability
  • set_arrangement_clip_lengthno sensitive capability
  • set_arrangement_clip_positionno sensitive capability
  • set_clip_nameno sensitive capability
  • set_clip_warp_modeno sensitive capability
  • set_device_parameterno sensitive capability
  • set_device_routingno sensitive capability
  • set_locatorno sensitive capability
  • set_loopno sensitive capability
  • set_tempono sensitive capability
  • set_track_armno sensitive capability
  • set_track_muteno sensitive capability
  • set_track_nameno sensitive capability
  • set_track_panno sensitive capability
  • set_track_sendno sensitive capability
  • set_track_solono sensitive capability
  • set_track_volumeno sensitive capability
  • start_playbackno sensitive capability
  • stop_clipno sensitive capability
  • stop_playbackno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ableton-mcp-suite/badge.svg)](https://mcptrustchecker.com/registry/ableton-mcp-suite)
HTML
<a href="https://mcptrustchecker.com/registry/ableton-mcp-suite"><img src="https://mcptrustchecker.com/registry/ableton-mcp-suite/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ableton-mcp-suite/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ableton-mcp-suite --online --registry pypi

Use the free API → How scoring works

More in Design & Media