Skip to main content
Glama
298,399 tools. Last updated 2026-07-14 12:39

"Sanic" matching MCP tools:

  • Check if Sonic Pi is running and discover its active port by verifying the boot log and Spider server port status. Safe to call anytime without sending OSC messages.
    MIT
  • Trigger sync points in Sonic Pi code by sending an OSC cue. Specify a path like /trigger/drop to start live_loops or one_shot blocks waiting for synchronization.
    MIT
  • Save a Sonic Pi song to the library with an auto-incremented version number. Each song is stored as a new version in a folder named after the song.
    MIT
  • Instantly stop all currently playing sounds, including GUI-started buffers, to silence Sonic Pi audio output.
    MIT
  • Set the master volume using an amplitude multiplier from 0.0 (silence) to 5.0 (may clip), with 1.0 as unity gain.
    MIT

Matching MCP Servers

  • Start audio recording of Sonic Pi output via PipeWire. Returns the output path for use with record_stop to end the capture.
    MIT
  • List all songs in the library, or filter by name to view versions of a specific song.
    MIT
  • Stops an active PipeWire recording and saves the audio file to disk using the output path provided by record_start.
    MIT
  • Save a reusable Sonic Pi code snippet to a specific category in the pattern library for quick reuse.
    MIT
  • Sum left and right audio channels to create a mono master output for checking mix balance and compatibility.
    MIT
  • Enable a high-pass filter on the master output to remove low-frequency rumble by setting a cutoff frequency in Hz.
    MIT
  • Enable a low-pass filter on the master output by setting a cutoff frequency in Hz to soften high frequencies.
    MIT
  • Run Ruby code in a specified Sonic Pi buffer (0-9) to organize live_loops across multiple slots, mirroring GUI buffer tabs.
    MIT
  • Load a song from the library by folder name and optional version number. Use 0 for the latest version.
    MIT
  • Retrieve the most recent errors and warnings from Sonic Pi's server log after executing code. Use this to identify and debug runtime issues.
    MIT