bandsaas
mcpotherLicense your music to AI on your terms, and run your whole artist business. 46 tools, keyless.
run it
on your own machines, one way per deploy method# once, as root:
docker build -t mcp-local/bandsaas:latest https://github.com/jyswee/bandsaas.git
#!/usr/bin/env bash
# bandsaas (io.github.jyswee/bandsaas), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-bandsaas.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-bandsaas -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/bandsaas:latest
[Unit]
Description=MCP server bandsaas (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/bandsaas
WorkingDirectory=/var/lib/mcp/bandsaas
ExecStart=/opt/mcp/my-agent/bin/bandsaas.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/bandsaas
[Install]
WantedBy=multi-user.target
docker build -t bandsaas https://github.com/jyswee/bandsaas.git docker run --rm -p 127.0.0.1:8101:8000 bandsaas
# Generated by Hub for toolset "my-agent" (2026-10-18T03:19:03+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
bandsaas:
build:
context: https://github.com/jyswee/bandsaas.git
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
:8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
volumes:
npm-cache: {}
uv-cache: {}
# Generated by Hub for toolset "my-agent" (2026-10-18T03:19:03+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: bandsaas
namespace: mcp
labels: &id001
app: bandsaas
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: bandsaas
image: CHANGE_ME
ports:
- containerPort: 8000
name: http
env: []
---
apiVersion: v1
kind: Service
metadata:
name: bandsaas
namespace: mcp
spec:
selector:
app: bandsaas
ports:
- port: 8000
targetPort: http
name: http
# Generated by Hub for toolset "my-agent" (2026-10-18T03:19:03+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
bandsaas:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: bandsaas
image: CHANGE_ME
ports:
- containerPort: 8000
name: http
env: []
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- cloud run
-
Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.
Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.
connect to it
copy what your client needs{
"mcpServers": {
"bandsaas": {
"command": "CHANGE_ME",
"args": []
}
}
}
#!/usr/bin/env bash # Registers every server with Claude Code (run once; `claude mcp list` to check). set -euo pipefail set -a; [ -f .env ] && source .env; set +a claude mcp add bandsaas -- CHANGE_ME
{
"mcpServers": {
"bandsaas": {
"command": "CHANGE_ME",
"args": []
}
}
}
{
"servers": {
"bandsaas": {
"type": "stdio",
"command": "CHANGE_ME",
"args": []
}
}
}
name: my-agent target: local servers: - hub: io.github.jyswee/bandsaas
- no recipe for target 'local': fill the files by hand
tools · 2
bandsaas_get_startedExplains what BandSaaS is and how to activate this MCP server (no API key on this session yet).Explains what BandSaaS is and how to activate this MCP server (no API key on this session yet).
pin 4870b44c5d9d5de9ecb1ce5e9f646492e326b2987c4ca6acad939502fec62882bandsaas_signupCreate 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.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.
pin bb9932af2d9a1f88dabe3d0f451f28147d902d0253fc6326bff08a04621e53c8
runs · 1
the latest tests of this entry by the hub and its workers, newest first| date | worker | method | status | sandbox | reason |
|---|---|---|---|---|---|
| 2026-10-16 09:46 | local-mac | remotemcp 2025-11-25 | ok2 tools | none | — |