Skip to main content
Glama
kvoltmer

Audionaut MCP Server

by kvoltmer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Audionaut MCP Server

No user-submitted related servers found.

    Related Servers

    • openDAW MCP

      ameobius-ai
      A
      license
      B
      quality
      B
      maintenance
      MCP server for headless, agent-native control of openDAW, enabling programmatic music production with tracks, instruments, effects, MIDI, automation, and rendering via 543 tools.
      6
      100
      Apache 2.0

    • PampaPilot MCP Server

      LeoLisena
      F
      license
      A
      quality
      B
      maintenance
      MCP server for controlling REAPER digital audio workstation from natural language. It enables AI agents to create tracks, import audio, adjust mix parameters, and manage sessions through typed operations and a REAPER bridge.
      22
      -

    • Podcast MCP

      calebn
      A
      license
      D
      quality
      B
      maintenance
      Enables podcast producers and agents to manage multitrack projects, run per-track transcription, perform transcript-driven edits, process audio via FFmpeg, and inspect a read-only DAW timeline over MCP.
      160
      MIT

    • reaper-mcp

      vecnode
      A
      license
      B
      quality
      C
      maintenance
      This MCP server enables AI assistants to control a live REAPER DAW instance, including transport, tracks, FX, MIDI, media, markers, rendering, and project state, with an escape hatch for arbitrary ReaScript commands.
      40
      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 22 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, from project creation to clip gain/fades and stem separation. The main overlaps are request_feature vs report_bug (same GitHub issue mechanism, different intent) and the referenced but missing delete_region, which complicates remove_clip/cleanup_regions boundaries.

    Naming Consistency4/5

    The set mostly follows a readable verb_noun pattern: get_project_info, create_project, place_clip, remove_track, report_bug. Minor deviations exist for clip_gain, clip_speed, clip_fades, and one-word tools like analyze/split, but these remain understandable.

    Tool Count4/5

    22 tools is on the high side but reasonable for a DAW-like audio project server covering project, track, clip, region, analysis, export, and support operations. A few operations could likely be consolidated, but most tools earn their place.

    Completeness3/5

    Core workflows are covered: create/import/export, analyze, edit clips and regions, and remove tracks/channels. However, notable gaps remain, including no explicit track/channel create or rename operations, no project tempo/metadata update tool, and a delete_region operation referenced in remove_clip but absent from the tool list.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources