Skip to main content
Glama
nickcapron

creaper

by nickcapron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to creaper

No user-submitted related servers found.

    Related Servers

    • ReaperMCP

      xDarkzx
      A
      license
      B
      quality
      A
      maintenance
      Connects AI assistants to REAPER for music production, enabling full control over tracks, MIDI, mixing, mastering, and audio analysis through 153 tools across 24 modules.
      174
      93
      Apache 2.0

    • Scythe MCP REAPER

      yura9011
      F
      license
      B
      quality
      C
      maintenance
      Enables AI-powered music composition and control for REAPER DAW through OSC and ReaScript integration. Supports transport control, MIDI generation, track management, and music theory operations like scales, chords, and rhythm patterns.
      17
      -

    • reaper-mcp-bridge

      Echo722
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-capable AI agents to control REAPER through typed tools and a Lua escape hatch for project creation, track management, recording and editing, MIDI writing, mixing, rendering, and batch operations.
      50
      MIT

    • flstudio-mcp

      rosasynthesiz
      A
      license
      A
      quality
      C
      maintenance
      AI control for FL Studio via the Model Context Protocol — full in-DAW mixing (Mix Doctor diagnosis, gain staging, EQ/compression/reverb, reference matching), routing, and composition through Claude and any MCP client. 67 tools. Windows.
      67
      33 PyPI
      83
      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/5.0

    Scored across 125 tools

    Disambiguation3/5

    Many tools have overlapping purposes: add_midi_notes can write melodies/basslines just like write_melody/write_bassline, add_drum_pattern overlaps with add_genre_groove, and multiple analysis tools (analyze_audio, measure_tracks, compare_mix_to_style) target similar measurement goals. Descriptions are detailed and often explicitly guide selection, but the sheer number of similar-sounding options creates real risk of misselection.

    Naming Consistency3/5

    All names use snake_case, but the convention is mixed: many are verb_noun (get_project_overview, add_fx), some are single verbs (record, transport, undo), and others are noun phrases (sample_folders, new_project_tab). Verb choices vary widely (get/list/analyze/check/measure/compare/add/create/write/build), so the pattern is readable but not predictable.

    Tool Count1/5

    125 tools is far beyond any reasonable scope and well above the 50+ threshold for an extreme mismatch. Even though the server covers a broad domain, the set is too large for an agent to efficiently select from, forcing constant cross-referencing and increasing the chance of wrong tool choice.

    Completeness4/5

    The surface is remarkably comprehensive, covering project management, track/folder/bus creation, MIDI and audio editing, mixing, mastering, composition, theory, sampling, vocals, recording, templates, and exports. Minor gaps exist (e.g., no general MIDI export, no track template deletion, limited project tab management), but most workflows have clear paths.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources