Skip to main content
Glama
Sign In
LaurentHuzard

beat-twin

by LaurentHuzard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to beat-twin

No user-submitted related servers found.

    Related Servers

    • ableton-live-mcp

      jterratsdev
      A
      license
      B
      quality
      B
      maintenance
      Local MCP server for inspecting and controlling Ableton Live through a local HTTP bridge. Enables LLMs to perform production workflows like MIDI import, track editing, mixing, mastering, and export.
      59
      21 npm
      MIT

    • ableton-agent-mcp

      ju5tinz
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes Ableton Live control (session state, transport, tracks, devices, clips, MIDI note editing) as tools for LLM agents, enabling natural language manipulation of a Live session.
      1
      MIT

    • Ableton MCP Server

      ntworm
      A
      license
      B
      quality
      A
      maintenance
      Local Python MCP server for inspecting and automating Ableton Live Sets, including MIDI editing, device control, audio analysis and groove tools. Connects MCP clients to a MIDI Remote Script and extension bridge on the user’s machine.
      97
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target distinct resources (arrangement, session, browser, clip, device, scene, track, transport), but 'bitwig_session_inspect' is broad and could overlap with track/device status tools, though descriptions clarify its role.

    Naming Consistency5/5

    All tools follow a consistent pattern: domain prefix (bitwig_, browser_, clip_, etc.) plus descriptive snake_case verb phrase, making the surface predictable and easy to navigate.

    Tool Count5/5

    With 14 tools covering key aspects of a DAW (arrangement, transport, tracks, devices, clips, browser), the count is well-scoped for a read-only integration.

    Completeness3/5

    The read-only surface covers inspection of many elements, but lacks write/mutate tools for actual control, and the 'plan' tool suggests a gap where no apply tool exists.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources