io.github.jyswee/bandsaas
License your music to AI on your terms, and run your whole artist business. 46 tools, keyless.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport sse bandsaas 'https://mcp.bandsaas.com/sse' --header 'Authorization: <Optional BandSaaS band key as a bearer token: '\''Bearer bsk_...'\''. Not required — without one the server starts in keyless onboarding mode and an agent can self-sign-up via the bandsaas_signup tool.>'
{
"mcpServers": {
"bandsaas": {
"type": "sse",
"url": "https://mcp.bandsaas.com/sse",
"headers": {
"Authorization": "<Optional BandSaaS band key as a bearer token: 'Bearer bsk_...'. Not required — without one the server starts in keyless onboarding mode and an agent can self-sign-up via the bandsaas_signup tool.>"
}
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
BandSaaS — Remote MCP
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
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:
{
"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:
{
"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):
| Music | Merch | Events / ticketing |
|---|---|---|
| Fan subscriptions | Crowdfunding | Site design |
|---|---|---|
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.
Frequently asked questions
What is io.github.jyswee/bandsaas?
License your music to AI on your terms, and run your whole artist business. 46 tools, keyless.
How do I install io.github.jyswee/bandsaas?
It runs as a remote server. In Claude Code: claude mcp add --transport sse bandsaas 'https://mcp.bandsaas.com/sse' --header 'Authorization: <Optional BandSaaS band key as a bearer token: '\''Bearer bsk_...'\''. Not required — without one the server starts in keyless onboarding mode and an agent can self-sign-up via the bandsaas_signup tool.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.jyswee/bandsaas need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is io.github.jyswee/bandsaas open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.jyswee/bandsaas?
It is published by jyswee. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.