Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt

Use this file to discover all available pages before exploring further.

The official Patchline plugin for Claude (Code + Desktop). Wraps the MCP server with a Patchline-specific progressive-interview workflow for music release planning — Claude asks structured questions, drafts each rollout phase, and saves outputs back to your Patchline catalog.   Free to install. Tool calls consume your AI credit pool.

​
Why use the plugin vs. raw MCP

The MCP server gives Claude access to Patchline’s product tools. The Claude plugin adds:
  • Progressive interview workflow — Claude walks you through 8 lifecycle phases (Creative Brief → Release Plan → Pitch Kit → Visual Assets → Smart Links → Release Day → Post-Release → Catalog Integration), asking only the questions needed at each phase.
  • Lifecycle-phase skills — each phase has a dedicated skill (e.g., aria:release-plan, aria:pitch-kit, aria:rollout) that knows the right tools to call and the right output format.
  • Project state in Patchline — outputs auto-save back to your Patchline project anchor.
  • Slash commands for common actions.
If you’re using Claude for music work, the plugin is the right start. For pure tool access (no workflow), use raw MCP.

​
Install on Claude Code

1

Add the marketplace

/plugin marketplace add Patchline-AI/aria
2

Install the plugin

/plugin install aria@patchline-ai
/reload-plugins
3

Authenticate

/mcp
Then authenticate plugin:aria:aria. Browser opens for OAuth.
4

Start a project

/aria:start
The plugin walks you through bootstrapping a music project workspace.

​
Install on Claude Desktop

Add to your claude_desktop_config.json: 
{
  "mcpServers": {
    "aria": {
      "url": "https://www.patchline.ai/api/mcp/v1",
      "transport": "http"
    }
  }
}
Restart Claude Desktop. The plugin’s slash commands surface in the chat input.

​
Slash commands

Once installed, the plugin exposes these slash commands inside Claude:
CommandWhat it does
/aria:startBootstrap a new project workspace
/aria:nextAdvance to the next lifecycle phase
/aria:audio-intakeUpload + analyze a finished track
/aria:creative-briefCapture vision, audience, success metric
/aria:vision-storyDefine sonic identity + narrative
/aria:songwriting-briefPre-recording: concept + references
/aria:moodboardBuild sonic + visual references
/aria:release-planGenerate the full rollout
/aria:pitch-kitPer-track DSP pitches
/aria:smart-linkRouting links + pre-saves
/aria:rolloutWeek-by-week content calendar
Each command knows which MCP tools to call and which Patchline data to read.

​
How a project flows

The plugin enforces a lifecycle: 
start → audio-intake (if track exists) ─┐
       └→ songwriting-brief (if no track) ┴→ creative-brief →
                                              vision-story →
                                              moodboard →
                                              release-plan →
                                              pitch-kit →
                                              smart-link →
                                              rollout →
                                              [release day] →
                                              [post-release]
Each phase produces a markdown deliverable saved to your .patchline/ workspace AND back to the Patchline project anchor.

​
Pricing

TierPlugin accessPer-tool credit costs
All tiersFreeStandard tool credit costs apply
The plugin itself is free. It’s a thin workflow layer over the MCP server.

​
Repo & support

​
FAQ

The plugin includes the MCP server. Don’t install both separately — you’ll get duplicate tool listings. Pick one (plugin if you use Claude, raw MCP for other clients).
No. The plugin connects to your Patchline workspace. You need a free account at minimum.
Yes — /aria:start and the plugin’s own help system walk you through every command in context.
The lifecycle is a default, not a requirement. You can skip phases or run them out of order. Each phase skill works standalone.