Content Tools
play.band
Manages play.band tenant accounts and site settings, including handle availability, claiming handles, and updating branding, copy, and streaming links.
ENDPOINT 1
https://play.band/mcp
MCP server metadata
- Name
- play.band
- Version
- 1.0.0
Known tools 24
get_site_settingsRead site branding, copy, and homepage options for the authenticated tenant
Inferred read-onlyupdate_site_settingsPatch site branding, copy, streaming links, and homepage options
Inferred read-onlyactivate_premiumDocumentation only — purchase Premium via REST POST /v1/billing/premium with x402 USDC on Base
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.play-band]
url = "https://play.band/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"play-band": {
"type": "http",
"url": "https://play.band/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: play-band
Remote MCP URL: https://play.band/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"play-band": {
"url": "https://play.band/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"play-band": {
"type": "http",
"url": "https://play.band/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "play-band",
"transport": "streamable-http",
"url": "https://play.band/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.