Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_session_infoB
Get information about REAPER. Note: OSC is primarily for sending commands.
Use this to confirm connection is working.
set_tempoA
Set the project tempo in BPM.

Args:
    tempo: Tempo in beats per minute (20-999)
playB

Start playback.

stopB

Stop playback.

recordB

Start recording.

goto_positionB
Move cursor to a specific position.

Args:
    seconds: Position in seconds
create_trackB
Create a new track.

Args:
    name: Name for the new track
set_track_volumeB
Set track volume.

Args:
    track_number: Track number (1-based, as shown in REAPER)
    volume: Volume level (0.0 = -inf dB, 1.0 = 0 dB)
set_track_panB
Set track pan position.

Args:
    track_number: Track number (1-based)
    pan: Pan position (-1.0 = full left, 0.0 = center, 1.0 = full right)
mute_trackB
Mute or unmute a track.

Args:
    track_number: Track number (1-based)
    muted: True to mute, False to unmute
solo_trackB
Solo or unsolo a track.

Args:
    track_number: Track number (1-based)
    solo: True to solo, False to unsolo
arm_trackA
Arm or disarm a track for recording.

Args:
    track_number: Track number (1-based)
    armed: True to arm, False to disarm
select_trackC
Select a track.

Args:
    track_number: Track number (1-based)
create_midi_itemB
Create a MIDI item on a track.

Args:
    track_number: Track number (1-based)
    position: Start position in beats
    length: Length in beats (default: 4 = 1 bar in 4/4)
add_notesA
Add MIDI notes to an existing MIDI item.

Args:
    track_number: Track number (1-based)
    item_index: Index of the MIDI item (0-based)
    notes: List of note dictionaries with:
        - pitch: MIDI note number (0-127, middle C = 60)
        - start: Start position in beats (relative to item)
        - duration: Duration in beats
        - velocity: Velocity (1-127, default 100)
execute_luaA
Execute arbitrary Lua code in REAPER.

This gives full control over REAPER via ReaScript.
The code runs in REAPER's Lua environment with access to the reaper.* API.

Args:
    code: Lua code to execute

Example:
    execute_lua("reaper.ShowMessageBox('Hello from MCP!', 'Test', 0)")
trigger_actionB
Trigger a REAPER action by name.

Available actions:
- Transport: play, stop, pause, record, rewind, forward
- Project: save, save_as, new_project, undo, redo
- Tracks: insert_track, delete_track, duplicate_track
- View: zoom_fit, toggle_mixer

Args:
    action_name: Name of the action to trigger

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 17 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. Tools like add_notes, create_midi_item, and create_track handle different MIDI/track creation tasks, while transport controls (play, record, stop) and track controls (mute_track, solo_track, arm_track) are well-separated. Even execute_lua and trigger_action serve different automation purposes without overlap.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern throughout. Examples include add_notes, arm_track, create_midi_item, get_session_info, and set_tempo. The naming is predictable and readable, with no deviations in style or convention.

Tool Count5/5

With 17 tools, the set is well-scoped for a DAW control server, covering essential operations like transport, track management, MIDI editing, and automation. Each tool earns its place without bloat, providing comprehensive control over REAPER's core functionalities in a manageable number.

Completeness5/5

The tool surface offers complete coverage for DAW operations, including CRUD for tracks and MIDI items, transport controls, track state management (mute/solo/arm/volume/pan), tempo setting, and advanced automation via execute_lua and trigger_action. There are no obvious gaps that would hinder agent workflows in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues