Bandsaas

io.github.jysweePublished by GitHub account jysweev1.3.0Updated Oct 24, 2026

License your music to AI on your terms, and run your whole artist business. 46 tools, keyless.

The publisher's own server: Vips

Overview

AI-generated overview

BandSaaS is a remote MCP server for musicians that lets an assistant register tracks, issue and revoke AI licences, pull compliance evidence, and run an artist’

What you can do
Register tracks by ISRC and issue, revoke and review AI licences, including an access log of granted and blocked use
When to use it
Useful for artists or their teams who want an assistant to manage AI licensing of their catalogue and produce compliance evidence, or to run the wider artist business from an agent. Keyless onboarding makes it easy to try before committing.
Requirements
Remote SSE endpoint; no install. No key needed to start: the session begins with get_started and signup tools. An existing band passes a bsk_ key as an Authorization bearer header. Signup needs the human's email and a band name, plus a card via Stripe for the 7-day trial.
Before you install
Signup sends a welcome and activation email to the given address and requires a card through Stripe for the free trial; writes stay gated until the owner completes that check. The returned API key is shown once. Tools can create and change band data, issue or revoke licences, and export compliance evidence.

Installation

In SourceWeft

  1. Open Bandsaas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jyswee%2Fbandsaas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bandsaas": {
      "type": "sse",
      "url": "https://mcp.bandsaas.com/sse"
    }
  }
}

README

BandSaaS — Remote MCP

[MCP] [Remote] [Auth] [Website]

License your music to AI — on your terms. The first artist platform with built-in AI licensing, exposed to your agent as a remote MCP server.

Your copyright, enforced. And the whole artist platform comes with it.

AI companies are training on the world's music. BandSaaS is the platform that lets an artist register every track by its ISRC, issue per-use licences to the AI agents that want to read or reproduce it, revoke them, and pull a provable audit trail of exactly who accessed the work — and who was blocked. This remote MCP server puts that copyright moat, and the entire artist business behind it, directly inside any MCP-capable agent.

Works with: Claude Code · Claude Web · Claude Desktop · Cursor · ChatGPT · Cline · Windsurf · Raycast · any MCP client

[Watch: license a track to AI from your agent]

Register a track by its ISRC and issue an AI licence — from your agent. Watch full-res »

  • Endpoint: https://mcp.bandsaas.com/sse
  • Health: https://mcp.bandsaas.com/health
  • Server card: https://mcp.bandsaas.com/.well-known/mcp/server-card.json
  • Auth: none required — keyless onboarding built in.

The copyright moat (A2A AI-licensing)

Five tools turn your agent into the control plane for who may train on your music:

  • bandsaas_register_track — register a recording (by ISRC) to the agent-to-agent copyright registry.
  • bandsaas_issue_licence — grant a scoped licence (read / summarise / reproduce) to another AI agent.
  • bandsaas_revoke_licence — pull a licence back.
  • bandsaas_licensing_access_log — a provable, tamper-evident log of every access — granted and blocked.
  • bandsaas_licensing — the licensing overview.

It's how an AI agent can legally read or reproduce a track — while the artist stays in control and gets paid. Every upload is screened for originality and registered with A2A Infrastructure; AI companies need a licence key to access the music.

…and the compliance evidence to prove it

Five more read-only tools turn that audit trail into regulator-ready evidence — the paperwork an AI company (or its lawyers) needs to show its training data was licensed:

  • bandsaas_compliance — a point-in-time compliance snapshot.
  • bandsaas_compliance_posture — an at-a-glance posture check across the copyright controls.
  • bandsaas_compliance_frameworks — assessment mapped to the EU AI Act, NIST AI RMF, SOC 2, Colorado SB24-205 and GDPR.
  • bandsaas_compliance_audit_events — the OCSF audit event stream (filter by allowed / blocked).
  • bandsaas_compliance_export — export the evidence as a portable file.

…and the whole artist platform comes with it

BandSaaS is a multi-tenant platform where musicians build a site and sell music, merch, tickets, fan subscriptions and crowdfunding — keeping ~95% of revenue via Stripe Connect. This server exposes that whole surface as 46 tools — exact parity with the bss CLI's per-band agent surface, plus the AI-licensing and compliance suite — led by bandsaas_tai, a built-in AI band manager with full context of the artist's catalog, merch, events, fans and settings. Ask it "which track should I release next?" or "draft a tour announcement" and it advises and takes safe actions on the artist's behalf.

Keyless onboarding

No signup friction. A fresh agent starts with two tools — bandsaas_get_started and bandsaas_signup. After self-signup the full 46-tool set unlocks in place (via notifications/tools/list_changed). Signup returns a scoped bsk_ key that works immediately for reads; writes stay gated until the human owner completes the 7-day-free-trial card check ($0 today), so the abuse surface is zero. The agent never handles a tenant ID — it's derived from the key.

Connect

Remote — no install:

json
{  "mcpServers": {    "bandsaas": { "url": "https://mcp.bandsaas.com/sse" }  }}

With a key (for an existing band), pass the bsk_ key as a bearer token if your client supports headers:

json
{  "mcpServers": {    "bandsaas": {      "url": "https://mcp.bandsaas.com/sse",      "headers": { "Authorization": "Bearer bsk_yourband_..." }    }  }}

Try it (no key, no install): connect to https://mcp.bandsaas.com/sse, call bandsaas_get_started, then bandsaas_signup with a band name + email.

See it in action

Every part of the business, driven from an agent (click any thumbnail for the full-res video):

Structured output

Every JSON-returning tool declares an outputSchema and returns structuredContent on tools/call, so directory scanners and typed clients get machine-readable results, not just text. (46 / 46 tools carry an outputSchema.)

Docs

  • LISTING-KIT.md — canonical copy/metadata for every MCP-directory listing + the full 46-tool inventory.
  • server.json — MCP registry manifest.

License

Proprietary — Tyga.Cloud Ltd. See LICENSE.

Source: README.md at commit b904510

Tools

2

bandsaas_get_started

Explains what BandSaaS is and how to activate this MCP server (no API key on this session yet).

Takes no parameters.

bandsaas_signup

Create a new BandSaaS band/site. Requires the human's email and a band name: a welcome + activation email is sent to them (card required via Stripe to start the 7-day free trial, nothing charged during it). Returns an API key (shown once) and unlocks all BandSaaS tools in this session immediately. Ask the human for their email and band name before calling.

ParametersemailrequiredgenrebandNamerequiredfirstName

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Vipsallowed integrations