Skip to main content
Glama

Related Servers

Alternatives to omnidaw-agent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to control a browser-based digital audio workstation (openDAW) for music production, including track creation, effects, MIDI, automation, and rendering.
      100
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read, patch, and render DAW projects (REAPER, FL Studio, .rpp/.dawproject) and to measure WAV audio metrics such as peak, RMS, LUFS, and stereo width. It closes the loop by applying patches, rendering before/after audio, and scoring the results against an intent so music-production models can be trained and verified.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with reversible DAW control for music production, enabling inspection of instruments and parameters, batch edits, and evaluated revision runs with audio feedback and rollback.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to read and control a DAW through typed tools covering session and transport state, tracks, mixer channels, MIDI parts and notes, supported plugin parameters, and finite editing operations, while also offering offline song inspection and WAV analysis.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and scripts to edit, convert, repair, separate, tune, transcribe, notate, mix, and master audio through stable versioned JSON commands, with provenance sidecars and replayable, reproducible results. Every capability is exposed as tooling an agent can chain without a GUI, including dry runs, schema introspection, and pass/fail quality gates.
      5
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Control Logic Pro locally on macOS through MCP: transport, tracks, mixer, plug-in parameters, audio analysis, bounce and delivery, with optional gesture and voice control. Uses OSC, CoreMIDI and macOS Accessibility. Actions report confirmed, uncertain or failed outcomes. Actual control requires a local Mac with Logic Pro. Hosted/Linux builds are schema inspection only; all operations are disabled.
      12
      3
      MIT

    TDQS

    B3.1/5.0

    Scored across 115 tools

    Disambiguation3/5

    The core DAW tools mostly target distinct resources and actions, but there is meaningful overlap between transport_get and tempo_get, transport_set_tempo and tempo_set_map, and jobs_wait versus agent_wait. The large agent_* family (agent_preview, agent_apply, agent_arrange_preview, agent_arrange_timeline, agent_measure, agent_export_preview) also duplicates native arrangement, mastering, analysis and export operations, making boundaries unclear. An agent can often tell tools apart, but the parallel native/preview/agent layers create real misselection risk.

    Naming Consistency4/5

    Most tools follow a predictable domain_action snake_case pattern (tracks_list, clips_write_midi, mixer_set_send, devices_add), which is easy to scan. Minor deviations exist, such as agent_* tools using a different naming style and some domain_verb forms like transport_play versus noun-like session_info, but the overall convention is stable.

    Tool Count1/5

    115 tools is far beyond a well-scoped surface, even for a DAW with many domains. The large agent_* preview/wrapper family adds substantial duplication on top of already complete native tools, making the set unwieldy and hard to navigate.

    Completeness4/5

    The surface covers an unusually broad DAW lifecycle: transport, tracks, session clips, arrangement, automation, devices, MIDI FX, mixer, theory, audio analysis, mastering, export and jobs. Gaps are minor, such as no explicit scene delete, limited note-level editing, and no track group/ungroup operation, but most workflows can be completed or worked around.