Music360 MCP
Connect agents to Music360 so they can read and act on artists, musical works, phonograms, contracts, shows, and operational tasks from one MCP remote.
Overview
Music360 MCP is a MCP server for the Build phase that exposes the Music360 API to agents for artists, works, phonograms, contracts, shows, tasks, and related music-business data over streamable-http.
What is this MCP server?
- Music360 API surface for artistas, obras, fonogramas, contratos, shows, and tarefas via MCP
- Streamable-http remote at app.music360.com.br/mcp with SVG branding in manifest
- Version 1.2.0 with public GitHub repository music360app/music360app
- Targets AI agents managing Brazilian music-industry catalogs and show operations
- Suited to rights, release, and tour/task workflows rather than generic file storage
- Manifest version 1.2.0
- Remote URL https://app.music360.com.br/mcp (streamable-http)
- Open-source reference at github.com/music360app/music360app
What problem does it solve?
Your music ops agent needs Music360 entities in chat, but maintaining custom API wrappers and context packing for every entity type slows indie shipping.
Who is it for?
Indie builders and small teams automating Music360-backed catalogs, contract lookups, show planning, or task triage inside Claude Code or Cursor.
Skip if: Developers with no Music360 account, purely consumer streaming apps, or workflows that only need royalty analytics from other PROs without Music360.
What do I get? / Deliverables
After registering the Music360 MCP remote, your agent can call platform-aligned tools while you focus on product workflows and UI.
- Agent-callable Music360 tools for repertoire and operations data
- Faster Build cycles for music SaaS features without bespoke MCP boilerplate
- Documented remote endpoint aligned with Music360 MCP manifest version 1.2.0
Recommended MCP Servers
Journey fit
Music360 MCP is installed while you are building backends or agent features that must talk to a live music-rights and operations platform. Integrations covers vendor-hosted MCP servers that map a product API (Music360) into standard tools for coding agents.
How it compares
Vendor music-operations MCP API, not a local Claude skill for mixing or a generic SQLite music library script.
Common Questions / FAQ
Who is br.com.music360.app/mcp-server for?
Solo builders and small music-business product teams who use Music360 and want MCP-native access for AI agents handling artists, works, phonograms, contracts, shows, and tasks.
When should I use br.com.music360.app/mcp-server?
Use it during Build when you are wiring agent tooling or internal automations that must read or update Music360 records through a supported remote MCP endpoint.
How do I add br.com.music360.app/mcp-server to my agent?
Add the streamable-http remote https://app.music360.com.br/mcp in your MCP client and configure Music360 authentication per their platform docs and the music360app GitHub repository.