Bandcamp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Cotlet.dev API key. Required for Codex, Claude Code, and calling the optional local MCP wrapper helpers; the hosted ChatGPT/Claude connectors can authenticate via OAuth instead. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Bandcamp through Cotlet.dev. Call bandcamp_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bandcamp_guideA | How to work in Bandcamp (read releases, sales and merch orders, update stock and manage download codes): its screens and the sign-in link. Call this first. |
| bandcamp_statusA | Check that your Cotlet.dev account and Bandcamp are ready: account, credits and Bandcamp connection. |
| bandcamp_openA | Open a Bandcamp page in your signed-in Cloud Browser (default https://bandcamp.com) to work with read releases, sales and merch orders, update stock and manage download codes. |
| bandcamp_readC | Read the current Bandcamp page: its text and numbered buttons, links and fields. |
| bandcamp_clickC | Click a numbered element on the current Bandcamp page. |
| bandcamp_typeB | Type text into a numbered field on the current Bandcamp page. |
| bandcamp_closeA | Close the Bandcamp browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.