Bandcamp MCP Server
Sales, merch orders, releases and fan messages for your Bandcamp page.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/bandcamp'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Bandcamp API and MCP server: Let your AI agent run your Bandcamp merch and sales.
Bandcamp has an API for sales reports and merch orders, given by email to labels and fulfillment partners, and no MCP server (checked 27 Oct 2026). Releases, discount and download codes, refunds and fan messages have no endpoints. Cotlet runs 13 Bandcamp tools hosted, over MCP for agents and REST for scripts.
Read Bandcamp releases, sales and merchandise records through MCP or REST. Connect your artist or label account to an agent, reporting workflow or script.
- Free 7-day trial, no card
- Unofficial, not affiliated with Bandcamp
- Page: https://cotlet.dev/integrations/bandcamp-api-mcp-server
What can you automate in Bandcamp?
- Mark merch orders shipped
- Update stock after a show
- Sales report per release
- Create a discount code
- Generate download codes
- Message your followers
Does Bandcamp have an MCP server or an API?
- The developer page says: "Labels and merchandise fulfillment partners can interact with their accounts via the Bandcamp API. To register for API use, contact us." A solo artist account has no path in.
- The API has no webhooks. New orders come from polling, and a token lasts one hour.
- Zapier and n8n have no Bandcamp app. The official links are ShipStation order sync and Bandcamp Sync for Shopify, a beta for Pro and Label accounts.
| What you need | Bandcamp API | ShipStation, Shopify sync | Cotlet |
|---|---|---|---|
| Who can use it | Approved labels and partners | Shopify sync: Pro or Label | Any artist or label account |
| Mark orders shipped with tracking | Yes | Skips Bandcamp's email | Yes, after your OK |
| Set merch stock | Yes | Matched by SKU only | Yes |
| Sales reports | Yes | No | Yes |
| Discount and download codes | No | No | Yes, after your OK |
| Refunds, prices, Community messages | No | No | Yes, after your OK |
Checked 27 Oct 2026. Sources: Bandcamp API: getting access, Bandcamp Sales Report API, Bandcamp Merch Orders API, Bandcamp Sync for Shopify, Bandcamp Help: Integrating with ShipStation
How does Cotlet connect to Bandcamp?
- Sign in to Bandcamp. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Bandcamp password, and no shipping email, refund or fan message goes out before you approve it.
Connect Bandcamp to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Turn on Bandcamp for agents. Create a Cotlet account, log in to your artist or label account in its Cloud Browser and press Enable for agents.
- Add the Cotlet address. Add https://cotlet.dev/mcp/v1 to the MCP servers or connectors of your agent.
- Allow the connection. Chat apps open a Cotlet sign-in. Code editors, n8n and scripts send an API key made in the console.
Bandcamp shares https://cotlet.dev/mcp/v1 with every other app you turn on. If you enable Bandcamp after the agent is connected, refresh the connector to load its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-bandcamp \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-bandcamp": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-bandcamp]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: bandcamp_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: bandcamp_write
How to use the Bandcamp REST API
Create your Cotlet API key
Sign in to Bandcamp in its Cotlet Cloud Browser and enable the app for agents. Use an artist or label login rather than a fan-only account.
Create a Cotlet API key with access to Bandcamp and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Make your first Bandcamp API request
cURL: list_releases:
curl https://cotlet.dev/api/v1/bandcamp/releases \
-H "Authorization: Bearer $COTLET_API_KEY"
Read releases and preserve sales units
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "bandcamp",
"tool": "list_releases",
"result": {
"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"
}
]
}
}
Read result.releases; release listing has format and visibility filters without pagination inputs. The default selection includes public, private and draft releases.
Price, revenue and net amounts use major currency units with a currency field, not cents. Sales rows can represent sales, payouts or reversals; preserve type and quantity.
Merchandise quantities are specific to options and shipping origins. A null quantity_available means unlimited, not zero.
Bandcamp workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read releases and a dated revenue-summary export into a sales sheet that preserves currency. |
| Make | HTTP > Make a request | Read unshipped merchandise orders into a packing-preparation list without marking shipped or refunding. |
| Python or Node.js | REST API | Read merchandise stock into an option-and-origin review that retains unlimited quantities as null. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Bandcamp; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Bandcamp API endpoints and MCP tools
Merch orders and stock
Counts are kept per shipping origin and per size or color. Refunds work on physical orders from the last 180 days that are not under a dispute.
- List merch orders (
list_merch_orders, read): Orders from your Merch Orders page with items, buyer and shipping address. - Mark order shipped (
mark_order_shipped, write, asks first): Mark a merch order shipped; Bandcamp emails the buyer with the tracking number and note. - Refund merch order (
refund_merch_order, write, asks first): Refund a physical order from the last 180 days and optionally return the item to stock. - List merch items (
list_merch_items, read): Merch items with price, SKU, quantity sold and quantity available, per option. - Update merch quantity (
update_merch_quantity, write): Set how many of a merch item or option are available.
Sales and reports
The three Tools page reports, dated in UTC like Bandcamp's own exports.
- List sales (
list_sales, read): Sales line items for a date range, with the net amount of each. - Export sales report (
export_sales_report, read): One of the three reports from your Tools page for a date range.
Releases, codes and fans
Download codes come in batches of 100 and count against your code allowance. A Community message reaches every follower by email and in the app.
- List releases (
list_releases, read): Albums and tracks on your account with price, release date and visibility. - Update release (
update_release, write, asks first): Change the price, title or release date of an album or track. - Create discount code (
create_discount_code, write, asks first): New discount code that fans enter in the Buy Now dialog. - List track/album codes (
list_track_album_codes, read): Your code batches with how many are redeemed; with batch_id, the codes of one batch. - Generate track/album codes (
generate_track_album_codes, write, asks first): New batch of one-use codes fans redeem for a download, counted against your code allowance. - Send Community message (
send_community_message, write, asks first): Post a message to your Community page; followers get it by email and in the Bandcamp app.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/bandcamp-api-mcp-server#tools
Who can see my Bandcamp session, and how do I revoke it?
- What we store. Your logged-in Bandcamp profile, AES-256-GCM, kept in Finland. No password.
- What your agent gets. 13 Bandcamp tools. No cookie, no login.
- What the session sees. Your store: buyers' names and addresses, sales, followers.
- What no tool touches. PayPal payouts, uploads, deleting releases, your password.
- If Bandcamp logs you out. You get an email with a link to log in again. We never do it for you.
- How to cut access. Disable for agents, reset the browser or delete the API key.
Grades of A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.
Is it against Bandcamp's terms? Account safety
Not to scrape any text, media, or other data or content from the site, including through the use of scripts, robots, bots, spiders, scrapers, crawlers, or other automated means; ... Not to train any machine learning or AI model using content on our site or otherwise ingest any data or content from Bandcamp's platform into a machine learning or AI model.
The Terms of Use (effective 7 May 2026) make this policy binding and let Bandcamp restrict an account "without notice". Read strictly, an AI agent reading your own sales is data going into an AI model, so Bandcamp could object to any agent, ours or one on GitHub. The removals reported in 2026 follow the January ban on AI-generated music; we found no account closed for a store tool or an MCP server (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own artist or label account, logged in by you
- One Cloud Browser with a steady IP and its own cookies
- Shipping emails, refunds, codes and fan messages wait for your OK
- Only your own store, never the public catalog
- If Bandcamp objects, we pause the Bandcamp tools for everyone within 24 h
Mark a big post office run shipped in batches over the evening, not hundreds of orders in a minute, and keep one Community message per sale.
What happens when Bandcamp changes?
- 12 h between tests of the Bandcamp reads and stock tools
- 24 h between tests of shipping emails and fan messages
- $0 for a call to a Bandcamp tool paused for repair
If Bandcamp redesigns Merch Orders or the Tools page, we change the tool and your agent keeps the same calls. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads unshipped orders. Buyer, city and items of each open order.
- Pairs each parcel. By name and city; a close match is held back.
- Waits for your OK. The batch shows up in your Cotlet console.
- Reports what is left. Marked, held and late orders, with reasons.
| Action | Undo |
|---|---|
| Mark an order shipped | No, the fan already has the email |
| Refund a merch order | No, the money is back with the fan |
| Send a Community message | No, followers got it by email |
| Generate download codes | No, they count against your allowance |
| Change a price or title | Yes, set the old value back |
| Set merch stock | Yes, set the old number back |
6 of 13 tools ask first: everything a fan sees or pays for. update_merch_quantity runs at once, because a stock number reaches nobody and one more call restores it. Turn the wait off per tool when a run is scheduled.
Bandcamp sends the shipping email the moment an order is marked shipped, with the tracking number and note in it.
MCP call:
{
"name": "mark_order_shipped",
"arguments": {
"order_id": "4471025938",
"tracking_number": "9400111899223344556677",
"note": "Thanks for the support! Your LP is on its way."
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/bandcamp/orders/4471025938/shipped/mark \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"tracking_number":"9400111899223344556677","note":"Thanks for the support! Your LP is on its way."}'
Tool output:
{
"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
}
]
}
A script or a cron job calls the same tools over REST at /api/v1/bandcamp, with the same key and price. A refund on an order older than 180 days fails, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the Bandcamp MCP server cost?
About $12 a month for an artist shipping about 25 merch orders a month, 2,080 credits. Bandcamp keeps its revenue share as before.
| Job | Calls | Credits |
|---|---|---|
| Mark merch orders shipped, twice a week | 4 × 8 | 320 |
| Take merch table sales off stock | 8 × 2 | 160 |
| Low stock check, weekly | 1 × 4 | 40 |
| Sales report per release and artist | 3 × 1 | 30 |
| Discount code and Community post | 3 × 1 | 30 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,080 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on a free artist account, no Pro or Label plan
Bandcamp publishes no average per artist, so the month is our example: 8 post office runs, 2 shows, one sale, one report. The merch item on Bandcamp averages about $19. Dollars at the $29 pack rate.
Bandcamp MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Venut-Technologies/bandcamp-mcp | Search, genre tags, albums, labels and tracks, anonymous and read only. MIT, last commit 25 Sep 2026. | The public catalog only: no orders, sales or stock. |
| leosakharoff/bandcamp-mcp | Python discovery server with lyrics and tag browsing, 3 stars. | Public catalog, last commit 16 Jan 2026. |
| mtl-bandcamp-mcp (MusicTech Lab) | Five read tools over the monthly CSV exports you save to a folder, March 2026. | Read only, you export by hand; its GitHub repo answers 404 today. |
| Apify Bandcamp scrapers | Public release data through Apify's MCP, paid per 1,000 results. | Nothing inside your account. |
| ShipStation, Bandcamp Sync for Shopify | Official order and stock sync. | Orders and stock only; ShipStation skips Bandcamp's shipping email. |
No GitHub server we found logs in to a seller account. For listening and digging, a discovery server is free and enough. For orders and stock alone, ShipStation or Shopify sync are official. For codes, refunds, reports and fan messages from an agent, Cotlet works in the store you already run.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Bandcamp tools go to contact@cotlet.dev.
Bandcamp API and MCP: questions
Can I use the Bandcamp API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, pick Bandcamp under Integrations in the console and log in to your artist or label account in its Cloud Browser. The trial starts with your Cotlet account, with no card.
How do I connect Bandcamp to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Bandcamp once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Bandcamp account through Cotlet, in their phone apps too.
What can ChatGPT do in Bandcamp?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Bandcamp: mark merch orders as shipped with tracking; monthly sales report per release and per artist; update merch stock after a show. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Does Bandcamp have webhooks?
No. The label API is polled for new orders, and an artist account has no events at all. Run your agent on a schedule instead, for example list_merch_orders every evening.
Does it work without Bandcamp Pro?
Yes. Cotlet works on a free artist account. Pro features stay Pro: targeted messages by location or spend, and Shopify inventory sync.
Can it read my fans' collections or the public catalog?
No. The tools work only in your own store: your releases, orders, sales, codes and Community page.
Is the MCP server different from the REST API?
Only the way in. Both carry the same 13 tools with the same inputs, answers, key and price. Agents call MCP; scripts and HTTP steps call REST.
Is Cotlet affiliated with Bandcamp?
No. Cotlet is independent and not affiliated with Bandcamp.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.