Skip to main content
Glama
Sign In
fender-studio-mcp

fender-studio-mcp

by b4blue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to fender-studio-mcp

No user-submitted related servers found.

    Related Servers

    • studio-one-mcp

      NeanderthalMan
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that lets Claude and other MCP clients read PreSonus Studio One .song files directly and drive a running Studio One through an in-app bridge device. It exposes tools for songs, tracks, takes, markers, transport, mixer channels, meters and roughly 1,000 Studio One commands.
      27
      39 npm
      12
      MIT

    • logic-mcp

      Imtylerrrrrr
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code to operate Logic Pro — transport, track selection/mute/solo/arm, mixer volume and pan, 8-band Channel EQ, and insert plugin slots — by emulating a Mackie Control surface over a CoreMIDI virtual port. Every command is verified against the LED, fader, and LCD feedback Logic sends back, so results report whether each action actually took effect.
      MIT

    • fender-studio-mcp

      maaatheeew
      A
      license
      Not graded
      quality
      C
      maintenance
      An unofficial MCP server that lets an agent control Fender Studio Pro / PreSonus Studio One — transport playback, Mackie Control mixer moves, shortcut-driven track and session editing, plug-in listing and insert-macro generation, and DAW command discovery and dispatch from an exported key scheme. It also ships audio-to-MIDI workflows for drafting drums or a hummed melody from rehearsal recordings before arranging them in the DAW.
      1
      MIT

    • Cubase MCP

      neox69
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude or any MCP client to view and control a Cubase/Nuendo project in real time, including transport, tempo, locators, mixer, channel strip, inserts, plug-in parameters, and 1,454 commands. It also supports music generation and recording notes into tracks.
      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

    B3.4/5.0

    Scored across 59 tools

    Disambiguation3/5

    Most tools target distinct Studio One resources and actions, but there is meaningful overlap: live_command duplicates many specialized commands, live_events/live_edit_events/live_track_edit all modify events, and live_tracks/live_events/live_notes are easy to confuse for inspection. The detailed descriptions help, but the large surface still creates real selection ambiguity.

    Naming Consistency4/5

    The naming is mostly consistent snake_case with recognizable prefixes: live_ for the running Studio One, song_ for saved song files, and audio_ for capture/analysis. Some tools use noun-style getter names while others use verb_style action names, but the pattern remains readable and predictable overall.

    Tool Count2/5

    At 59 tools, the surface is very heavy for an MCP server and well beyond the typical 3-15 range. The DAW domain is broad, but many operations could be consolidated, especially given the generic live_command escape hatch and several overlapping inspection/edit tools.

    Completeness4/5

    The surface covers a wide range of Studio One workflows: transport, tracks, events, notes, mixer channels, inserts, sends, markers, arranger sections, automation, recording, undo/redo, snapshots, and audio analysis. Minor gaps remain, such as no explicit song creation/open/close and no mixdown or stem export, but most workflows are reachable.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources