# Bandcamp API and MCP server

> Bandcamp has an API, but only for labels and merchandise fulfillment partners, who get access by emailing Bandcamp (checked 11 Oct 2026). It covers sales reports, merch orders, shipping status and stock; it has no calls for releases, discount codes, track/album codes, refunds or Community messages.

Online music store where artists and labels sell digital albums, tracks and merch directly to fans, with sales reports, discount codes, download codes and a Community page for messages.

## What is the Bandcamp API?

Cotlet's Bandcamp API exposes 13 endpoints for your own Bandcamp account: list releases, list sales, export sales report, list merch orders, list merch items, list track/album codes, mark order shipped, refund merch order, update merch quantity, update release, create discount code, generate track/album codes and send Community message. The list_releases endpoint returns albums and tracks on your account with price, release date and visibility. Each endpoint takes simple JSON inputs like since, until or release_id and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 13 (6 read, 7 write)
- **Updated:** 2026-10-11

Bandcamp has an API, but only for labels and merchandise fulfillment partners, who get access by emailing Bandcamp (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Bandcamp with 13 endpoints (6 read, 7 write): your AI agent signs in as you and does the work.

## Does Bandcamp have an official API?

Bandcamp has an API, but only for labels and merchandise fulfillment partners, who get access by emailing Bandcamp (checked 11 Oct 2026). It covers sales reports, merch orders, shipping status and stock; it has no calls for releases, discount codes, track/album codes, refunds or Community messages.

| Task | Bandcamp official | Cotlet |
|---|---|---|
| List sales and export sales reports | Partly: Sales Report API returns the sales report; revenue summary and payout statement are on the Tools page only | Yes |
| List merch orders | Partly: Merch Orders API, labels and fulfillment partners | Yes |
| Mark orders shipped with tracking | Partly: Merch Orders API, labels and fulfillment partners | Yes |
| Update merch quantity | Partly: Merch Orders API; Bandcamp Sync for Shopify also syncs inventory for Pro and Label accounts | Yes |
| Refund a merch order | No | Yes |
| Edit release price, title or date | No | Yes |
| Create discount codes, generate track/album codes | No | Yes |
| Message followers on your Community page | No | Yes |

Sources: [Bandcamp API: getting access](https://bandcamp.com/developer), [Bandcamp Sales Report API](https://bandcamp.com/developer/sales), [Bandcamp Merch Orders API](https://bandcamp.com/developer/merch), [How Bandcamp Sync for Shopify works (Help Center)](https://get.bandcamp.help/en/articles/15263055-how-bandcamp-sync-for-shopify-works), [Integrating with ShipStation (Help Center)](https://get.bandcamp.help/en/articles/15263354-integrating-with-shipstation), [Shipping label purchase with EasyPost (Help Center)](https://get.bandcamp.help/en/articles/15263041-introduction-to-shipping-label-purchase-on-bandcamp), [How do I issue a refund to my fan? (Help Center)](https://get.bandcamp.help/en/articles/15263325-how-do-i-issue-a-refund-to-my-fan)

## For AI agents

```text
Bandcamp has an API, but only for labels and merchandise fulfillment partners, who get access by emailing Bandcamp (checked 11 Oct 2026). It covers sales reports, merch orders, shipping status and stock; it has no calls for releases, discount codes, track/album codes, refunds or Community messages.
Cotlet provides a hosted MCP server and REST API for Bandcamp: 13 tools (6 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=bandcamp; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/bandcamp
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_releases, list_sales, export_sales_report, list_merch_orders, list_merch_items, list_track_album_codes, mark_order_shipped, refund_merch_order, update_merch_quantity, update_release, create_discount_code, generate_track_album_codes, send_community_message
Confirm      mark_order_shipped, refund_merch_order, update_release, create_discount_code, generate_track_album_codes, send_community_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/bandcamp-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=bandcamp (Bandcamp is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Bandcamp once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Bandcamp server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Bandcamp MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Bandcamp in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Bandcamp's terms; Cotlet is not affiliated with Bandcamp.
```

## What can an AI agent do in Bandcamp?

Cotlet is best for Bandcamp artists and labels who are not developers and want their AI agent to ship merch orders, report sales, adjust stock and run discount and download codes without running or fixing a server.

- **[Mark merch orders as shipped with tracking](https://cotlet.dev/integrations/bandcamp-api-mcp-server/mark-merch-orders-shipped)** (runs: daily): "Here is today's Pirate Ship export. Match each tracking number to my unshipped Bandcamp orders by buyer name and mark them shipped with a short thank-you note." → `list_merch_orders`, `mark_order_shipped`
- **[Monthly sales report per release and per artist](https://cotlet.dev/integrations/bandcamp-api-mcp-server/sales-report-per-release)** (runs: monthly): "Build last month's Bandcamp report: net revenue per release, split by artist on my label, with shipping, taxes and discount codes shown separately." → `export_sales_report`, `list_sales`
- **[Update merch stock after a show](https://cotlet.dev/integrations/bandcamp-api-mcp-server/update-merch-stock)** (runs: after each show): "We sold 9 black Night Drive LPs, 4 red ones and 11 tour tees (3 S, 5 M, 3 L) at the merch table last night. Take them off my Bandcamp stock and tell me what is low." → `list_merch_items`, `update_merch_quantity`
- **[Run a sale with a discount code and tell your followers](https://cotlet.dev/integrations/bandcamp-api-mcp-server/create-discount-code-and-announce)**: "Make a 20% code NIGHTDRIVE20 for the Night Drive album, digital and vinyl, valid until 31 October, and draft a Community message about it for me to approve." → `list_releases`, `create_discount_code`, `send_community_message`
- **Generate track/album codes in bulk**: "Generate 100 album codes for the Tour EP in a batch called tour-2026 and tell me how many are redeemed in my old batches." → `list_releases`, `generate_track_album_codes`, `list_track_album_codes`

## Can Bandcamp automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Bandcamp connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to mark merch orders as shipped with tracking, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/bandcamp/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/bandcamp/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/bandcamp/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/bandcamp/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Bandcamp.

### list_releases

Albums and tracks on your account with price, release date and visibility. Access: read. REST: `POST /api/v1/bandcamp/list_releases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `format` | enum | no | digital, physical or all. Default: all. |
| `visibility` | enum | no | public, private, draft or all. Default: all. |

Lists the releases on your account, the same items the Bulk Edit page shows. Filter by digital or physical and by public, private or draft. Use release_id from each item in the other tools.

Example response:

```json
{
  "releases": [
    {
      "release_id": "r_1840221",
      "title": "Night Drive",
      "format": "digital",
      "visibility": "public",
      "price": 9,
      "currency": "USD",
      "release_date": "2025-11-14",
      "url": "https://yourname.bandcamp.com/album/night-drive"
    },
    {
      "release_id": "r_1902254",
      "title": "Tour EP",
      "format": "digital",
      "visibility": "draft",
      "price": 5,
      "currency": "USD",
      "release_date": "2026-11-01",
      "url": "https://yourname.bandcamp.com/album/tour-ep"
    }
  ]
}
```

### list_sales

Sales line items for a date range, with the net amount of each. Access: read. REST: `POST /api/v1/bandcamp/list_sales`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | date | no | Start of the date range. Default: 30 days ago. |
| `until` | date | no | End of the date range. Default: today. |

Returns the lines of your raw data sales report, oldest first: each line is the sale of an item, a payout or a sale reversal. Use export_sales_report for the revenue summary or the payout statement.

Example response:

```json
{
  "sales": [
    {
      "date": "2026-09-03T18:22:11Z",
      "type": "sale",
      "item_type": "album",
      "item_name": "Night Drive",
      "quantity": 1,
      "currency": "USD",
      "net_amount": 8.5
    },
    {
      "date": "2026-09-04T09:10:42Z",
      "type": "sale",
      "item_type": "package",
      "item_name": "Night Drive (12\" vinyl)",
      "quantity": 1,
      "currency": "USD",
      "net_amount": 24.1
    }
  ]
}
```

### export_sales_report

One of the three reports from your Tools page for a date range. Access: read. REST: `POST /api/v1/bandcamp/export_sales_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report` | enum | yes | revenue_summary, payout_statement or raw_data. |
| `since` | date | no | Start of the date range. Default: 30 days ago. |
| `until` | date | no | End of the date range. Default: today. |
| `release_id` | string | no | revenue_summary only: limit the report to this release. |

Returns the report you pick: revenue_summary (gross and net revenue, shipping and tax for a release or the whole catalog), payout_statement (which sales are in each bulk payout) or raw_data. For revenue_summary you can narrow the report to one release.

Example response:

```json
{
  "report": "revenue_summary",
  "since": "2026-09-01",
  "until": "2026-09-30",
  "currency": "USD",
  "gross_revenue": 1842.5,
  "net_revenue": 1713.1,
  "releases": [
    {
      "release_id": "r_1840221",
      "title": "Night Drive",
      "net_revenue": 1204.3
    },
    {
      "release_id": "r_1902254",
      "title": "Tour EP",
      "net_revenue": 508.8
    }
  ]
}
```

### list_merch_orders

Orders from your Merch Orders page with items, buyer and shipping address. Access: read. REST: `POST /api/v1/bandcamp/list_merch_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unshipped_only` | boolean | no | Only orders not marked shipped. Default: true. |
| `search` | string | no | Buyer email, last name or Bandcamp payment ID. |
| `since` | date | no | Start of the date range. Default: 30 days ago. |
| `until` | date | no | End of the date range. Default: today. |

Lists physical orders from your Merch Orders page, newest first, with the items bought, the buyer, the shipping address and whether the order shipped. By default only unshipped orders. Search by email, last name or Bandcamp payment ID. Pass order_id to mark_order_shipped or refund_merch_order.

Example response:

```json
{
  "orders": [
    {
      "order_id": "4471025938",
      "ordered_at": "2026-10-08T14:03:00Z",
      "shipped": false,
      "buyer": {
        "name": "Maya Brandt",
        "email": "maya@example.com"
      },
      "ship_to": {
        "name": "Maya Brandt",
        "city": "Leeds",
        "country": "United Kingdom",
        "country_code": "GB"
      },
      "items": [
        {
          "title": "Night Drive (12\" vinyl)",
          "option": "Black",
          "quantity": 1
        }
      ]
    }
  ]
}
```

### list_merch_items

Merch items with price, SKU, quantity sold and quantity available, per option. Access: read. REST: `POST /api/v1/bandcamp/list_merch_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `low_stock_below` | integer | no | Only items with fewer available than this. |

Lists the merch on your account with price, SKU, how many were sold and how many are available. Items with sizes or colors list each option. Quantities are kept per shipping origin. An item with no limit shows quantity_available as null.

Example response:

```json
{
  "items": [
    {
      "item_id": "p_1154611570",
      "title": "Band Tote",
      "sku": "GGRA3-1",
      "price": 12,
      "currency": "USD",
      "quantity_sold": 4,
      "quantity_available": 6,
      "options": []
    },
    {
      "item_id": "p_175167691",
      "title": "Night Drive (12\" vinyl)",
      "sku": "ND-LP",
      "price": 25.5,
      "currency": "USD",
      "quantity_sold": 12,
      "quantity_available": 8,
      "options": [
        {
          "item_id": "o_1842702675",
          "title": "Black",
          "sku": "ND-LP-B",
          "quantity_sold": 9,
          "quantity_available": 3
        },
        {
          "item_id": "o_1842702676",
          "title": "Red",
          "sku": "ND-LP-R",
          "quantity_sold": 3,
          "quantity_available": 5
        }
      ]
    }
  ]
}
```

### list_track_album_codes

Your code batches with how many are redeemed; with batch_id, the codes of one batch. Access: read. REST: `POST /api/v1/bandcamp/list_track_album_codes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `batch_id` | string | no | Batch ID from a previous call. Returns the codes of this batch. |

Without batch_id, returns each batch with its release, size and redeemed count, as the Track/album codes section of your Tools page does. With batch_id, returns every code of that batch and whether it was redeemed.

Example response:

```json
{
  "batches": [
    {
      "batch_id": "b_0042",
      "batch_name": "tour-2026",
      "release_title": "Tour EP",
      "codes": 100,
      "redeemed": 37
    }
  ]
}
```

### mark_order_shipped

Mark a merch order shipped; Bandcamp emails the buyer with the tracking number and note. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/mark_order_shipped`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_merch_orders. |
| `tracking_number` | string | no | Tracking number shown to the buyer. |
| `note` | string | no | Note for the buyer in the shipping email. |

Marks one order shipped. Bandcamp then emails the buyer with the tracking number and note you pass. One order per call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "4471025938",
  "status": "shipped",
  "tracking_number": "9400111899223344556677",
  "note": "Thanks for the support! Your LP is on its way.",
  "buyer_notified": true,
  "items": [
    {
      "title": "Night Drive (12\" vinyl)",
      "option": "Black",
      "quantity": 1
    }
  ]
}
```

### refund_merch_order

Refund a physical order from the last 180 days and optionally return the item to stock. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/refund_merch_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_merch_orders. |
| `return_to_stock` | boolean | no | Put the item back into your inventory. Default: false. |

Refunds a physical order the way the "refund this order" link on the Merch Orders page does, and your revenue share adjusts. It works for orders placed in the last 180 days and not under a dispute; for older orders the call fails and you refund the fan yourself, for example through PayPal. Digital purchases are refunded through Bandcamp Support. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "4471025938",
  "status": "refunded",
  "restocked": true
}
```

### update_merch_quantity

Set how many of a merch item or option are available. Access: write. REST: `POST /api/v1/bandcamp/update_merch_quantity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Item or option ID from list_merch_items. |
| `quantity_available` | integer | yes | New stock level. 0 marks the item Sold Out. |
| `shipping_origin` | string | no | Shipping origin to change. Default: your main origin. |

Sets the available quantity of an item or one of its options at a shipping origin. Bandcamp lowers it by itself when an item sells, so use this when you also sell elsewhere. 0 marks the item Sold Out. It runs without asking first: it reaches no one and one more call sets the old number back.

Example response:

```json
{
  "item_id": "p_1154611570",
  "title": "Band Tote",
  "quantity_available": 40,
  "previous_quantity_available": 6
}
```

### update_release

Change the price, title or release date of an album or track. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/update_release`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | string | yes | Album or track ID from list_releases. |
| `price` | number | no | New price. |
| `title` | string | no | New title. |
| `release_date` | date | no | New release date. |

Changes the price, title or release date of one album or track, like the edit button on its page or the Bulk Edit page. Pass only the fields you want to change. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "release_id": "r_1840221",
  "title": "Night Drive",
  "price": 7,
  "currency": "USD",
  "release_date": "2025-11-14",
  "updated": [
    "price"
  ]
}
```

### create_discount_code

New discount code that fans enter in the Buy Now dialog. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/create_discount_code`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | The code fans type, e.g. summersale. |
| `percent_off` | integer | yes | Percent off the base price. 100 is not offered. |
| `applies_to` | enum | no | anything, anything_except_preorders, digital_only, physical_only or single_item. Default: anything. |
| `item_id` | string | no | Release or package ID when applies_to is single_item. |
| `expires_on` | date | no | Bandcamp disables the code on this day. |

Creates a discount code. The percentage applies to the base price of the item, never to shipping or taxes. Codes cannot take a release priced at zero, and 100% off is not offered. If you set expires_on, Bandcamp disables the code on that day. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "code": "summersale",
  "percent_off": 20,
  "applies_to": "single_item",
  "item_id": "r_1840221",
  "expires_on": "2026-08-31",
  "status": "active"
}
```

### generate_track_album_codes

New batch of one-use codes fans redeem for a download, counted against your code allowance. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/generate_track_album_codes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | string | yes | Album or track ID from list_releases. |
| `batch_name` | string | yes | Private label for the batch, e.g. tour-2026. |
| `count` | integer | yes | Multiples of 100, at least 100. |

Creates a batch of track/album codes for a release you choose. Codes come in multiples of 100 with a minimum of 100 per batch, never expire, and count against the code allowance shown on your Tools page. The batch name is private to you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "batch_id": "b_0042",
  "batch_name": "tour-2026",
  "release_id": "r_1902254",
  "codes_created": 100
}
```

### send_community_message

Post a message to your Community page; followers get it by email and in the Bandcamp app. Access: write, asks the user first. REST: `POST /api/v1/bandcamp/send_community_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `body` | string | yes | Message text. |

Posts a message under your artist name. Fans who follow you receive it by email and in the Bandcamp app, and it appears on your Community page. Fans need to follow you to receive messages and to buy a release before they can comment. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "cm_2207",
  "status": "published",
  "published_at": "2026-10-11T10:00:00+02:00"
}
```

## How do I connect Bandcamp to Claude Code, Codex or Cursor?

Connecting Bandcamp takes three steps: request access, sign in to Bandcamp once, then add one MCP server or call the REST API with the same key.

### Connect Bandcamp to your agent.

1. **Create an account** Sign up and add Bandcamp in the console. Your API key is there too.

2. **Sign in to Bandcamp once** Open the connect page from the console and sign in to Bandcamp the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

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

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

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

4. **Ask your agent** Ask in plain words. Your agent finds the Bandcamp tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Here is today's Pirate Ship export. Match each tracking number to my unshipped Bandcamp orders by buyer name and mark them shipped with a short thank-you note.
```

### Call Bandcamp from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/bandcamp/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/bandcamp/mark_order_shipped \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"order_id":"4471025938","tracking_number":"9400111899223344556677","note":"Thanks for the support! Your LP is on its way."}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "order_id": "4471025938",
  "status": "shipped",
  "tracking_number": "9400111899223344556677",
  "note": "Thanks for the support! Your LP is on its way.",
  "buyer_notified": true,
  "items": [
    {
      "title": "Night Drive (12\" vinyl)",
      "option": "Black",
      "quantity": 1
    }
  ]
}
```

## Why use Cotlet for Bandcamp?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Bandcamp yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Bandcamp changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Bandcamp MCP server on GitHub?

Yes. Community Bandcamp MCP servers exist on GitHub, usually maintained by one person, and many of them search the public catalog instead of running your artist account. You install one on your own computer and fix it yourself when Bandcamp changes. Cotlet hosts a server for your own account, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, sign it in to Bandcamp, add it to each MCP client | Request access, sign in to Bandcamp once, add one MCP server or API key |
| When Bandcamp changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Bandcamp session | In a file on your computer, readable by any program you run | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Tools fail until you sign in again by hand | We keep it alive; if Bandcamp logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Bandcamp changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Bandcamp API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Bandcamp API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Bandcamp account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Bandcamp yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Bandcamp tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Bandcamp in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Bandcamp's terms:** You use your own Bandcamp account and stay responsible for following Bandcamp's terms. Cotlet is independent and not affiliated with Bandcamp. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Bandcamp. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Bandcamp once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Bandcamp session would leave my computer.**

Cotlet keeps your Bandcamp session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need to be a label or get API approval from Bandcamp?**

No. Cotlet works in your own artist or label account and does not use Bandcamp's API, which Bandcamp grants on request to labels and fulfillment partners. You also do not need a Pro account, which Bandcamp Sync for Shopify requires.

**Can my agent refund an order?**

Physical orders from the last 180 days, yes: Bandcamp offers a refund link on the Merch Orders page for them, and refund_merch_order does the same. Orders under a dispute cannot be refunded through Bandcamp, and older orders you refund yourself, for example through PayPal. Digital purchases are refunded by Bandcamp Support.

**Can my agent post or send messages in Bandcamp without asking me?**

No. Every call to mark_order_shipped, refund_merch_order, update_release, create_discount_code, generate_track_album_codes or send_community_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_merch_quantity runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Bandcamp API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/bandcamp/{tool} from the HTTP Request node.