Skip to main content
Glama
Sign In
marconadas

fLMCP

by marconadas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fLMCP

No user-submitted related servers found.

    Related Servers

    • fl-mcp

      ae5n
      A
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server for FL Studio on macOS, enabling control of projects, transport, mixer, plugins, automation, and piano roll operations.
      MIT

    • fl-bridge-mcp

      LIBCSYS
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other MCP clients to control FL Studio over virtual MIDI, including transport, tempo, patterns, step sequencing, mixer and channel controls, and live note or chord playback, while reading some FL state back.
      -

    • flemcee

      tylerjharden
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables remote control and automation of FL Studio via the flapi Python client. It provides tools for managing transport, mixer tracks, pattern sequencing, and plugin parameters, allowing users to execute Python code directly within the FL Studio environment.
      2
      -

    • FL Studio MCP Server

      unicornwhodev-afk
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to control FL Studio on Windows through a local MCP server without cloud dependencies. Bridges MCP clients to FL Studio's Python scripting environment via file-based IPC for project management, transport control, and UI workflow automation.
      -
    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

    C2.7/5.0

    Scored across 160 tools

    Disambiguation2/5

    Many tools have overlapping responsibilities: channel_all/channel_info/channel_selected/ui_selected_channel, mixer_all_tracks/mixer_track_info/mixer_get_peaks, and fl_ping/fl_bridge_info/piano_roll_status all require careful reading to tell apart. The detailed descriptions help, but with 160 tools, an agent will frequently select the wrong read/status variant.

    Naming Consistency4/5

    The vast majority of tools follow a clear domain-prefix_snake_case pattern (transport_, channel_, mixer_, playlist_, piano_roll_), which is very predictable. Minor deviations like fl_ping, fl_call_raw, ui_selected_channel, and channel_all break the pattern slightly, but the overall convention is strong and readable.

    Tool Count1/5

    160 tools is an extreme surface area for an MCP server, even for a full DAW like FL Studio. This will impose significant context/token costs and make tool selection much harder; many read/status tools could be consolidated into parameterized or bulk endpoints.

    Completeness3/5

    The server covers a remarkably wide range of FL Studio capabilities: transport, patterns, channels, mixer, plugins, playlist, piano roll, project, and browser. However, there are notable gaps such as creating/removing channels or mixer tracks, inserting/replacing plugins, and editing existing automation clips, which are core DAW workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources