Google Antigravity

Google's agent app for Gemini models. Setup takes one extra step compared to the other desktop apps, because custom MCP servers are added by editing a config file instead of filling in a form.

Requirements

Download Max for Live DeviceProducer_Pal.amxd — for Ableton Live

• Ableton Live 12.3+ with Max for Live. Live 12.4 or later is recommended. On Live 12.3 these don't work:

  • writing clip automation (reading and clearing it still work)
  • loading a sample into Simpler
  • the Library tool (searching your library and listing plug-ins)
  • finding a preset by name outside a device's own presets (packs' drum kits, Sounds racks, custom folders)
  • opening a plug-in's editor window

  Use the version of Max bundled with Live, or make sure your standalone Max is up to date.

• Node.js 20+

• Google Antigravity (requires a Google account)

Producer Pal doesn't need the IDE version — the standard app is enough. The IDE works the same way if you'd rather use it (there's an "Install IDE" button in the top right of the app).

Installation Steps

No need to install the Producer Pal device yourself: in the last step, the AI sets up Live for you.

Or install the device yourself

Download Producer_Pal.amxd, the Producer Pal Max for Live device.

Open User Library (under Places) in Live's browser, go to Presets → MIDI Effects → Max MIDI Effect, and drag Producer_Pal.amxd into that folder:

Drag it from the Max MIDI Effect folder onto a MIDI track:

It should display "Producer Pal Running" or something isn't working.

Then finish the installation: click Finish installation… on the device (or Open Chat UI, then Settings → Installation), and click Install there to add the remote script (clip automation, undo, plug-ins).

Restart Live, then choose Producer Pal as a Control Surface in Settings → Tempo & MIDI, with Input and Output left as None.

More in Finish the Installation.

1. Open the MCP Config

Go to Settings → Customizations and find Installed MCP Servers. The Skills list above it is long, so collapse Skills or scroll past it. Click Open MCP Config:

That opens ~/.gemini/config/mcp_config.json in an editor. Antigravity has no in-app editor for custom MCP servers, so this file is the only way to add one.

Not the same file as Gemini CLI

Gemini CLI reads ~/.gemini/settings.json. Antigravity reads ~/.gemini/config/mcp_config.json. Same folder, separate configs — adding Producer Pal to one does not add it to the other.

2. Add Producer Pal

Option A: With npx (recommended). Allows flexible startup order and auto-reconnection:

{
  "mcpServers": {
    "producer-pal": {
      "command": "npx",
      "args": ["-y", "producer-pal@latest"]
    }
  }
}

Only need some of the tools?

Narrow the toolset and every conversation gets smaller:

{
  "mcpServers": {
    "producer-pal": {
      "command": "npx",
      "args": ["-y", "producer-pal@latest", "--tools", "core,clip,track"]
    }
  }
}

--tools keeps only what you list; --disable-tools drops what you list. Both take tool names (read-clip or ppal-read-clip) and group names: core, session, actions, live-set, track, scene, clip, device, advanced, and read-only. Run npx producer-pal@latest --list-tools to print the groups plus the tools the running device currently offers.

Withholding a tool also drops the part of the Producer Pal Skills that teaches it, so you stop paying for the tool's schema and its guidance in every conversation. --tools read-only cuts the skills text by more than half.

Unlike the other flags, this one is per client: the Chat UI and your other MCP clients keep the full toolset. ppal-connect is always kept, since it is how the AI connects and receives the skills.

One wrinkle with --tools: it keeps what you list by withholding everything else, and "everything else" is the tool list this copy of npx producer-pal knows, so a tool added in a newer Producer Pal stays enabled until you update. --disable-tools names tools directly, so it can withhold a newer tool even from an older copy; only its group names are limited to the ones above.

Option B: Direct HTTP. Requires the device running in Live first (install it yourself, see above), no auto-reconnection:

{
  "mcpServers": {
    "producer-pal": {
      "serverUrl": "http://localhost:3350/mcp"
    }
  }
}

Save the file, then click Refresh back in Customizations. Producer Pal should appear under Installed MCP Servers with its tools enabled:

3. Start Using Producer Pal

With Live open, start a conversation with "connect to ableton". Allow Producer Pal tools when Antigravity asks:

The first time, the AI sets up Live for you:

1. It installs the Producer Pal remote script.

2. Restart Live, then choose Producer Pal as a Control Surface in Settings → Tempo & MIDI, with Input and Output left as None.

3. Tell the AI when you're done. It installs the Producer Pal device and adds it to your Live Set (it asks first).

Check It Works

Once connected, the AI confirms it can see your Live Set. Try a first request that doesn't change anything:

What tracks are in my Live Set?

It should list your tracks. If it can't connect or gets something wrong, see Troubleshooting below.

Troubleshooting

If it doesn't work, see the Troubleshooting Guide.