Developers
LoopMaker developer resources.
Integrate agents with private, local music generation on Apple Silicon Macs.
Start here
LoopMaker MCP server (local stdio)
LoopMaker ships with a dependency-free MCP server. It lets Codex, Claude Code, and any stdio-capable MCP client queue, monitor, cancel, and find music generations inside the user's LoopMaker app. Prompts, model weights, lyrics, and audio never leave the Mac.
Codex
codex mcp add loopmaker -- \
/Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp
Claude Code
claude mcp add --transport stdio --scope user loopmaker -- \
/Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp
Generic MCP client configuration
{
"mcpServers": {
"loopmaker": {
"command": "/Applications/LoopMaker.app/Contents/Resources/mcp/loopmaker-mcp"
}
}
}
The app can also install these configurations itself: open LoopMaker → Settings → MCP → Install Available Clients.
Streamable HTTP endpoint
This website exposes an MCP server over Streamable HTTP for discovery and integration questions:
- Endpoint:
https://www.getloopmaker.com/mcp - Transport: Streamable HTTP (
POSTwith JSON-RPC 2.0 bodies; responses areapplication/json) - Protocol versions:
2025-06-18(latest) and2025-03-26 - Sessions: stateless; no
Mcp-Session-Idis issued - Authentication: none required
GETreturns405with a JSON body because no SSE stream is offered
Handshake example:
curl -s https://www.getloopmaker.com/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}'
This remote endpoint intentionally exposes read-only product and integration knowledge. Actual audio generation always runs on the user's Mac through the local stdio server above — never in the cloud.
Tool catalog
Remote endpoint tools (this website)
loopmaker_product_info— current product facts: platform, memory tiers, pricing, outputs, privacy boundary.loopmaker_when_to_use— best-fit and poor-fit jobs, plus how an agent should hand off to LoopMaker.loopmaker_mcp_setup— client-specific setup instructions for the local stdio server.loopmaker_workflow_guide— the async status → generate → poll → deliver workflow and Memory Saver behavior.
Local stdio server tools (inside the LoopMaker app)
loopmaker_status,loopmaker_launch_app,loopmaker_list_modelsloopmaker_generate,loopmaker_get_job,loopmaker_list_jobs,loopmaker_cancel_job,loopmaker_list_tracks
Read operations are annotated read-only; generation and cancellation are actions requiring client approval.
Agent workflow
- Call
loopmaker_statusand confirm the app reports Ready. - Queue one render with
loopmaker_generate(prompt required; lyrics, duration, quality mode, seed, BPM, key optional). - Poll
loopmaker_get_jobuntil status iscompleted,failed, orcancelled. - Report the local WAV path from the job results.
Renders are serialized so two agents cannot load competing models into unified memory. On Macs below 24 GB, Memory Saver caps duration at 60 seconds and phases the lyric planner and renderer separately.
Machine-readable formats
Every page on this site serves clean Markdown when requested:
curl -s https://www.getloopmaker.com/mcp/ -H 'Accept: text/markdown'
Responses use Content-Type: text/markdown; charset=utf-8 and carry Vary: Accept. Unsupported Accept types receive 406 Not Acceptable. Requests for paths that do not exist return a real HTTP 404 whose body lists recovery URLs.
Sources of truth for agents:
- llms.txt — curated index with when-to-use guidance
- sitemap.xml — all public URLs
Security and privacy boundaries
- The local MCP process talks only to
127.0.0.1using a per-install random token; the token is never returned to agents. - No prompts, lyrics, or audio are uploaded by either the stdio server or this website's endpoint.
- The remote endpoint validates browser
Originheaders and serves read-only information only.
Support
Questions about integrating LoopMaker with your agent or product? Contact Tarun Yadav through tarun-yadav.com.