By Patchline-AI
Lean music-operator skills for the aria MCP: drop a track to your storefront, pitch to playlists, make smart links, and grow your fanbase — each one grounded, single-job action. Install once, reload plugins, then say 'get started'.
Drop a song. The one-shot release flow: upload the master, let Patchline analyze it, give it a cover, and put it on the storefront. Use when the user says "drop my new single", "release this track", "put my song out", "I just finished a track, get it live", or pastes a local audio file and wants it shipped. Reuses start's Spotify-URL identity resolution if the artist isn't connected yet. MCP-grounded: get_asset_upload_link -> confirm_asset_upload -> manage_catalog_asset set_cover_art -> create_store_link.
Know and grow your fans. Pull a grounded read on the artist's audience — how many fans, where they are, which segments are converting — and tie it to storefront sales and share-link performance, with concrete next moves. Use when the user says "who are my fans", "where are my listeners", "how's my audience", "how are sales", "how's my storefront doing", "where should I tour/advertise", or "how do I grow my fanbase". MCP-grounded: get_audience_overview / get_audience_geo / get_fan_segments + get_store_analytics / get_surface_analytics. Aggregates only — never individual fan names or emails.
Make and share a smart link. Create a live patchline.ai share link for a released track (or a pre-release drop link), then hand back distribution-ready copy for socials, email, and bio — plus how to read its analytics later. Use when the user says "make a smart link", "give me a share link for <song>", "create a link to send fans", "link for my release", or "how's my link doing". MCP-grounded: create_smart_link / create_drop_link -> get_share_surface -> get_surface_analytics. The link URL must be live — no placeholders.
How to drive the Patchline MCP well. The operating manual for any agent (or human) working the aria toolset — where to start, which calls are cheap vs expensive, how the safety gates work (attribution confirmation, dry-run/confirmation-token mutations, no hard delete), and the grounding discipline. Use when the user says "how do I use the Patchline tools", "what can Aria do", "how should I work my catalog", "is this safe to run", "how do I clean up duplicates", "how do I import a track", or when you're unsure how to drive the MCP and want the rules before acting.
Pitch a track. Find the song in the catalog, ground it in real intelligence and real playlist data, draft a sendable pitch, and create a shareable curator pitch link. Use when the user says "pitch my track", "write a pitch for <song>", "help me get on playlists", "draft a curator pitch", or "make a pitch link for <song>". MCP-grounded: catalog_search/get_asset -> get_song_intelligence + get_artist_intelligence + find_playlists/inspect_playlist -> generate_pitch -> create_pitch_link. No invented playlists, curators, or metrics.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ship a music release end-to-end without leaving Claude Desktop, Cowork, or Claude Code.
Aria is a Claude plugin for Claude Code and Claude Desktop/Cowork that walks artists and managers through a release lifecycle from raw idea or finished track to pitched, released, and live on a smart link. Every artifact it produces is grounded in your real catalog and real streaming data via the Patchline MCP. No hallucinated playlists. No invented metrics.
# In Claude Code
/plugin marketplace add Patchline-AI/aria
/plugin install aria@patchline-ai
/reload-plugins
After /reload-plugins, approve the Aria MCP server if Claude Code asks.
Then run /mcp, choose plugin:aria:aria, and authenticate with your
Patchline account. Once the server shows connected, start in plain language:
get started
get_started reports what's in your workspace (artists, tracks, releases) and
the single best next action. From there, just say what you want — "drop my new
single", "pitch this track", "make a smart link", "how are my fans doing" — or
invoke a skill directly (/aria:drop, /aria:pitch, /aria:link,
/aria:fans). Nothing chains; each skill is a standalone, single-job moment.
On Claude Desktop/Cowork, install the same plugin package through the app's plugin flow and use the same natural-language prompts.
If you are iterating on the plugin itself and want Claude Desktop/Cowork to
load your local working copy instead of the published Patchline-AI/aria
release, see TROUBLESHOOTING - Testing unreleased changes from a local clone.
If /reload-plugins reports "not available on this environment", see
TROUBLESHOOTING - /reload-plugins says "not available on this environment".
Use the artist profile URL first, not a track, album, or playlist URL. If you do not have the Spotify profile URL yet, type the artist name and Aria will search your Patchline roster/index.
drop — take a finished track from a file to live on your storefront (upload → analyze → cover → store link)pitch — ground a catalog track and draft sendable playlist-submission copy + a pitch linklink — create and share a smart link for a track, with analyticsfans — direct-to-fan: audience overview, geography, segments, store/surface analyticsoperator — the operating manual for driving the MCP correctly (safety gates, grounding, token-frugality)aria MCP server — tools spanning catalog management, secure upload handoff, cover art, playlist targeting, artist intelligence, pitch generation, project/campaign creation, smart links, and audience analytics. Call get_started first if you're unsure where to begin.This is not a tool explorer, and it's not a 10-step waterfall. Each skill is a single grounded action: it calls the aria MCP to ground every fact in your real catalog, artist intelligence, and track analysis — no invented playlists, no hallucinated metrics — and gets one job done fast. Both solo artists and labels use them.
/reload-plugins and approve the Aria MCP server if prompted./mcp, authenticate plugin:aria:aria, and wait for it to show connected.get started (or call the get_started tool) — Aria reports what you have (artists, tracks, releases) and the single best next step./aria:drop, /aria:pitch, /aria:link, /aria:fans.Nothing chains — each skill is standalone and can run any time. Skills produce a written artifact only if you ask; the default is a concise inline report.
npx claudepluginhub patchline-ai/aria --plugin ariaPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Production-grade vibe coding suite. Structured workflows from discovery to deployment: start, build, ship, fix, refactor.
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.
Memory compression system for Claude Code - persist context across sessions
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.