Bandsintown vs Discogs MCP Server
A side-by-side look at the Bandsintown and Discogs MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bandsintown for art & culture work over a hosted endpoint; choose Discogs MCP Server for art & culture as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bandsintown when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
artist_events, events.
Choose Discogs MCP Server when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DISCOGS_PERSONAL_ACCESS_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 45/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | DISCOGS_PERSONAL_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 128 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Bandsintown | View Discogs MCP Server |
Tools & capabilities
Bandsintown tools 2
artist_eventsUpcoming events for an artist.eventsGlobal events filter.
Discogs MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bandsintown
{
"mcpServers": {
"bandsintown": {
"url": "https://gateway.pipeworx.io/bandsintown/mcp"
}
}
}
Discogs MCP Server
{
"mcpServers": {
"cswkim-discogs-mcp-server": {
"command": "npx",
"args": [
"-y",
"discogs-mcp-server"
],
"env": {
"DISCOGS_PERSONAL_ACCESS_TOKEN": "YOUR_DISCOGS_PERSONAL_ACCESS_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Bandsintown is categorized under Art & Culture and uses a remote HTTP/SSE transport. Discogs MCP Server belongs to Art & Culture and uses a local stdio subprocess. Pick Bandsintown for art & culture work and Discogs MCP Server for art & culture.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Bandsintown has no declared pricing — check the project's own site. Discogs MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bandsintown and cswkim-discogs-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bandsintown has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Discogs MCP Server has 48/100 (Fair) with 2 views, 0 installs and 128 GitHub stars.