Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

README.md
# Bandcamp MCP server for ChatGPT and Claude

Bandcamp offers an API for labels and merchandise fulfillment partners. The source page reports no official MCP server, checked 27 October 2026.
Cotlet.dev connects ChatGPT, Claude and other AI agents to your own signed-in Bandcamp artist or label account.

Source: [Bandcamp integration page](https://cotlet.dev/integrations/bandcamp-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=bandcamp).

## What can your agent do?

The live page describes 13 hosted business tools: 6 reads and 7 writes.
MCP routes reads through `bandcamp_read` and writes through `bandcamp_write`.

- `list_merch_orders`
- `mark_order_shipped`
- `refund_merch_order`
- `list_merch_items`
- `update_merch_quantity`
- `list_sales`
- `export_sales_report`
- `list_releases`
- `update_release`
- `create_discount_code`
- `list_track_album_codes`
- `generate_track_album_codes`
- `send_community_message`

Six writes ask for confirmation by default, configurable per tool. `update_merch_quantity` runs without asking first.
Marking an order shipped sends the buyer an email. Refunds return money, Community messages reach followers, and generated download codes count against your allowance.
Review these actions before approving them.
Sales amounts use major currency units with a currency field. Merchandise stock is per option and shipping origin; a null quantity means unlimited stock.
PayPal payouts, uploads, deleting releases and account settings are outside these tools.

## Example requests

> List my unshipped merchandise orders.

> Show sales for my latest release.

> Show merchandise options with low stock.

> List my download-code batches and redemption counts.

## Connect ChatGPT and Claude

1. [Get access to Bandcamp](https://cotlet.dev/signup?app=bandcamp).
2. Sign in to your own Bandcamp artist or label account in the Cotlet.dev Cloud Browser and enable Bandcamp for agents.
3. In ChatGPT, use Settings > Apps & Connectors > Create with `https://cotlet.dev/mcp/v1/connect` and OAuth.
4. In Claude, use Settings > Connectors > Add custom connector with the same URL.

## Connect Codex and Claude Code

Create an API key in the Cotlet.dev console and set `COTLET_API_KEY` in your environment.

Codex:

```toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

Claude Code:

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

## Optional local MCP wrapper

Python 3.10+, standard library only. This repository provides seven generic browser helpers over Cotlet.dev: `bandcamp_guide`, `bandcamp_status`, `bandcamp_open`, `bandcamp_read`, `bandcamp_click`, `bandcamp_type`, `bandcamp_close`.
These local helpers are separate from the hosted business tools and routes above. Listing helpers needs no key; calling them requires `COTLET_API_KEY`.

```bash
export COTLET_API_KEY="your-key"
python3 bandcamp_agent.py serve
```

For a local MCP client:

```json
{"mcpServers":{"bandcamp":{"command":"python3","args":["/absolute/path/to/bandcamp_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}
```

Other commands: `connect`, `status`, `guide`, `read`, `tools`.
The read command opens the browser, reads the page and closes the browser session.

## Access and independence

Use your own Bandcamp artist or label account. You complete sign-in and any verification yourself.
Disable Bandcamp for agents, reset the browser or delete the API key to revoke access.
Cotlet.dev is independent and is not affiliated with, endorsed by or sponsored by Bandcamp.

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

Most tools are clearly distinct: read, click, type, open, and close map to separate browser actions. The three setup-ish tools (guide, status, open) have some conceptual overlap since all are called early, but their descriptions distinguish instructions, account readiness, and starting a browser session.

Naming Consistency5/5

All tool names use the same bandcamp_ snake_case prefix and concise action-oriented names. The pattern is predictable across the set, even where guide and status are nouns rather than verbs.

Tool Count5/5

Seven tools is well-scoped for a browser automation server: guidance, readiness check, open, read, click, type, and close each earn a place. There is no obvious bloat or missing setup step.

Completeness4/5

The core lifecycle is covered: orient, verify account, open, inspect, interact, and close. Minor gaps exist around explicit navigation, waiting, or scrolling, though these may be handled through clicking links and re-reading the page.