New in LoopMaker One-click MCP setup →

LoopMaker for AI agents

Your agent can make
the music.

Connect Codex, Claude Code, or another MCP client to LoopMaker.
Turn a brief into a finished local WAV—without a cloud generation service.

Included with LoopMaker · Local stdio server · Apple Silicon

AGENT BRIEF

“Make a warm synth-pop track at 104 BPM with intimate English vocals.”

Generating locally Warm synth-pop · 30 seconds
68%
  1. Lyrics and structure planned
  2. 2Native Apple Silicon render
  3. 3Export 24-bit WAV
OUTPUT ~/Library/Application Support/LoopMaker/tracks/warm-synth-pop.wav

Private by design

The server talks only to LoopMaker on your Mac. Prompts and tracks stay local.

Built for long renders

Jobs run asynchronously, so agents can poll progress or cancel safely.

Full creative controls

Prompt, lyrics, duration, BPM, key, language, seed, and render tier.

How it works

Delegate the wait.
Keep the creative call.

LoopMaker gives agents a predictable interface for a compute-heavy local workflow.

From brief to local file

The agent starts one job, checks it when useful, then returns the result.

Async by design
  1. 01

    Describe

    Turn the musical brief into one structured generation request.

    loopmaker_generate
  2. 02

    Render

    Manage the queue, memory tier, progress, and safe cancellation.

    loopmaker_get_job
  3. 03

    Hand off

    Return the local WAV path and effective render settings.

    status: completed

Made for an 18 GB Mac

Lyrics stay enabled while heavy models take turns in unified memory.

1

Plan lyrics0.6B MLX planner

2

Release memoryClear model cache

3

Render audioMLX + chunked VAE

Memory Saver · Fast tier · one render

Small surface, full workflow

Eight tools cover readiness, generation, progress, cancellation, and results.

Setup

Connect from LoopMaker.
One click.

The app discovers supported clients and installs the bundled local server. No npm package, service account, or API key.
Recommended

Install from the app

Open LoopMaker Settings, choose MCP, then install Codex, Claude Code, or every available client.

  1. 1

    Open LoopMaker → Settings

  2. 2

    Select the new MCP tab

  3. 3

    Click Install Available Clients

GeneralModelsMCPUpdatesLicense

LoopMaker MCPBundled and ready

Ready

CodexAI coding agent

Install

Claude CodeAI coding agent

Install

Command-line setup

Prefer to configure it yourself?

Run the matching command after installing LoopMaker in Applications.
CCodex
codex mcp add loopmaker -- \
  /Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp
AClaude Code
claude mcp add --transport stdio \
  --scope user loopmaker -- \
  /Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp
MOther MCP clients
{
  "mcpServers": {
    "loopmaker": {
      "command": "/Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp"
    }
  }
}
TRY THIS FIRST

“Check LoopMaker, generate a 30-second warm synth-pop song with these lyrics, and poll until the WAV is ready.”

Tool reference

Everything the agent
is allowed to do.

Read operations are separated from actions that launch, generate, or cancel.
loopmaker_status

Check the backend, selected model, memory tier, and privacy boundary.

Read
loopmaker_launch_app

Open LoopMaker when needed and wait briefly for the local engine.

Action
loopmaker_list_models

Inspect downloaded engines, supported tiers, and memory guidance.

Read
loopmaker_generate

Queue one text-to-music render and receive a job ID immediately.

Action
loopmaker_get_job

Read progress, effective settings, failures, and the final WAV path.

Read
loopmaker_list_jobs

Review agent-started jobs in the current LoopMaker session.

Read
loopmaker_cancel_job

Stop queued or running work at the next safe cancellation point.

Cancel
loopmaker_list_tracks

Find recent local WAV files without uploading or reading the audio.

Read

Local by design

The agent gets tools.
Not your audio library.

The MCP process reads LoopMaker’s random token at runtime and sends it only to the app on localhost. The token is never returned to the agent.
STAYS ON YOUR MAC
  • Prompts and lyrics
  • ACE-Step and MLX models
  • Generation jobs
  • Finished WAV files
127.0.0.1random local token
NOT REQUIRED
  • Cloud render queue
  • Generation API key
  • Audio upload
  • Per-track credits

MCP FAQ

Does the AI agent hear or upload my track?

No. Tools return status, settings, and a local path. Audio remains in LoopMaker’s local tracks directory.

Can two agents generate at the same time?

They can both queue work, but LoopMaker renders one job at a time to prevent overlapping model loads.

Why does the agent poll a job?

A local render can take minutes. Async jobs survive normal MCP timeouts and expose progress plus cancellation.

Does MCP work on an 18 GB Mac with lyrics?

Yes. Memory Saver runs the lyric planner and MLX renderer in separate phases, uses one Fast-tier take, and caps generation at 60 seconds.

Which MCP clients can connect?

LoopMaker supports one-click setup for Codex and Claude Code. Any client that launches a local stdio server can use the bundled executable.

LoopMaker app icon

Give the brief. Get the track.

MCP included · One-time $49 license · 30-day money-back guarantee