MCP.Market

Loom by SubverseLab MCP server

by senolsahan037-oss·io.github.senolsahan037-oss/loom·v0.4.4
No reviews yet

Reads your own Ableton projects and writes MIDI, chains and markers into a running Live set.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Loom by SubverseLab yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Loom by SubverseLab tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Loom by SubverseLab compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,243 servers

Install Loom by SubverseLab in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Loom by SubverseLab repository's README, as published. We do not edit it. Read it on GitHub

Loom

Loom is a measurement-based production system for Ableton Live by Şenol Şahan / SubverseLab: a local MCP server that reads your own .als projects and library, answers with counts instead of guesses, and writes MIDI, device chains, automation and arrangement markers into a running Live session, verifying every write by reading it back. <!-- mcp-name: io.github.senolsahan037-oss/loom -->

Canonical home: https://subverselab.com/loom · Cite: CITATION.cff · Licence: AGPL-3.0-or-later · Attribution: NOTICE.

Why it exists

Ask a general-purpose model what belongs on a kick drum and it answers with confidence, having never heard a record you made. Loom replaces that guess with evidence from three places: your own project archive (which devices you actually chain, which samples you actually reach for), real released records (genre evidence measured from audio, not described from memory), and the Live set that is open right now. Where the evidence runs out, a tool returns nothing and says so. Nothing is emulated, nothing is retried on an uncertain outcome, and every write is a dry run until you approve it.

There is one connection to Live: the Loom extension, an Ableton Extension running inside Live 12.4 beta. No Control Surface, no automatic fallback, no second writer path.

What is inside

No layer produces a guess: with no evidence there is no suggestion, what the SDK cannot do is not emulated, and every writing tool is a dry run by default.

Architecture, the canonical call flow and the bridge protocol: Docs/ARCHITECTURE.md.

Install (one path)

python3 install.py            # installs
python3 install.py --check    # changes nothing, reports state

install.py:

Antigravity), backing up each config; it is safe to re-run.

  1. Registers Loom with every MCP client it finds (Claude Desktop, Claude Code,

toolchain is present) and compares the version and bridge protocol of the extension installed in Live with this checkout. Live shows it as Loom, id subverselab.loom. An installed legacy package (loom.sensei-midi-writer) is reported: the MCP never sends it a mutation (LEGACY_EXTENSION).

  1. Prepares the extension package (extension/dist/loom.ablx, built if the
  1. Builds the catalogs from your own stock Ableton library.

Live's own step is a single one: add the .ablx in Live 12.4 beta's Extensions settings and restart Live. The extension opens a file bridge in its own storage directory; the MCP locates that bridge on every call.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Loom by SubverseLab: common questions

Is Loom by SubverseLab MCP server safe?
Mostly: it is graded B (83/100). Read the Loom by SubverseLab safety report
Does Loom by SubverseLab need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Loom by SubverseLab maintained?
The last commit was 42 days ago (2026-09-24). The latest release is v0.4.4.
What can I use instead of Loom by SubverseLab?
Servers from other publishers that do the same job: e2e MCP server.

Alternatives to Loom by SubverseLab

Same job from other publishers: the closest match first, then the best rated.

  • e2e
    Open live web and mobile app sessions from an e2e project to inspect the app and try locators.
    A