Live Prompting

Contents

• Demo with Claude Code
• Demo with cursor
• Installation
  • Install with Claude Code
  • Install with Cursor
  • Install with another AI tool
• Usage
  • Iteratively
  • On the fly
• What is live prompting?
• What is live coding?
• What is Sonic Pi?
• How this was developed

Demo with Claude Code

Here's a demo of how the MCP server looks with Claude Code!

Demo with Cursor

Here's a demo of how the MPC server looks with Cursor!

Installation

Note: This MCP server depends on Ruby version 3 or greater. If you do not already have it, use the rvm helper:

$ \curl -sSL https://get.rvm.io | bash
$ rvm install 3.4.5

To install, first open a terminal to clone this repository then retrieve dependencies.

$ git clone git@github.com:yevbar/live-prompting.git
$ bundle install

Be sure to remember where you cloned it or use the pwd command to get the path.

$ pwd
/Users/foobar/path/to/live-prompting

After which follow the relevant installation below.

Install with Claude Code

From a terminal, run the claude mcp command to add a new MCP server with the path to the cloned repository.

$ claude mcp add live-prompting -- ruby /Users/foobar/path/to/live-prompting/main.rb 

Install with Cursor

You can access the MCP configuration file either by clicking on the menu items Cursor > Settings > Cursor Settings > Tools & Integrations > "New MCP Server". Or by editing the file ~/.cursor/mcp.json in an editor of your choice.

You'll want to add the following contents:

{
  "mcpServers": {
    "live-prompting": {
      "command": "ruby",
      "args": ["/Users/foobar/path/to/live-prompting/main.rb"]
    }
  }
}

Install with another AI tool

If you'd like to install this MCP with another AI tool (ie Zed), what you're aiming to do is run the following command to start the server:

$ ruby /Users/foobar/path/to/live-prompting/main.rb

Usage

Open the Sonic Pi application in the background as well as your preferred tool whether that's Claude Code or a different AI product and you'll be good to go!

Iteratively

If you'd like to iteratively work on music, it's recommended you leverage a local Ruby script (defined in the play tool to be a .sonic.pi.rb file saved at the current working directory).

Rather than depend on the model to one-shot the entire song end to end each time, you can leverage a diff-based approach to tweak the song where you're interested.

Note: When accumulating multiple loops, you may find it better to restart rather than play over and over again. This helps ensure timing in loops or definitions are synced how you intend them.

On the fly

If you'd like to spin off a track or beat on the fly, then you can ask your agent to use the play_code_tool tool to play a generated snippet.

Note: If you want to continually generate new snippets or loops, you'll need to remember to use the same live_loop identifiers otherwise you end up overlaying loops into a cacophony.

What is live prompting?

A naming twist on live coding but via prompting rather than directly coding.

What is l

... View full README on GitHub