Bandsintown MCP Server

Tour dates, fan messages and stats for your Bandsintown artist page.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/bandsintown'

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

Bandsintown API and MCP server: Let your AI agent keep your tour dates right.

Bandsintown has no MCP server for artists. Its public API returns artist info and artist events with a key from your artist Settings, one key per artist, and writes nothing (checked 27 Oct 2026). Cotlet runs 11 Bandsintown tools hosted, over MCP for agents and REST for scripts, and 5 of them write.

Tour dates, fan messages and stats for your Bandsintown artist page. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Bandsintown
Page: https://cotlet.dev/integrations/bandsintown-api-mcp-server

What can you automate in Bandsintown?

Add tour dates from a spreadsheet
Match each date to the right venue
Move a show or mark it sold out
Publish drafts at announce time
Post to followers when tickets go on sale
Find cities with demand but no date

Does Bandsintown have an MCP server or an API?

Drafts, edits, deletes, posts to followers and Insights stay in the Bandsintown for Artists dashboard. The API docs list only the two reads.
Bandsintown's own ChatGPT app (June 2026, from directory listings) helps fans find concerts. It does not open your artist dashboard.
Zapier, n8n and Pipedream have no Bandsintown app (all three pages return 404). A community n8n node wraps the read API.

What you need	Public API	Bandsintown ChatGPT app	Cotlet
List your upcoming and past events	Yes, published only	Public listings	Yes, drafts too
Add, edit or delete events	No	No	Yes, edits after your OK
Post to followers	No	No	Yes, after your OK
Top markets, RSVPs, follower trend	Follower count only	No	Yes, from Insights
What you set up	API key from Settings	Fan side only	Your artist sign-in

Checked 27 Oct 2026. Sources: Bandsintown help: API documentation, Bandsintown help: What is the Bandsintown API?, Bandsintown help: Add an event, Bandsintown for Artists: Insights, Bandsintown help: Add multiple events at once, Bandsintown help: Edit events, Bandsintown help: Manage email notifications, Bandsintown Data Applications Terms of Use, Bandsintown ChatGPT app listing (mcptop)

How does Cotlet connect to Bandsintown?

Sign in to Bandsintown. 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 Bandsintown password, and no edit alert, publish or post reaches fans until you approve it.

Connect Bandsintown 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.

Enable Bandsintown for agents. Sign up, sign in to Bandsintown for Artists in its Cloud Browser and press Enable for agents.
Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector settings of your agent.
Confirm who you are. Chat apps open a Cotlet sign-in. Code editors, n8n and scripts use an API key from the console.

https://cotlet.dev/mcp/v1 serves Bandsintown and every other app you turn on in Cotlet. Enabled Bandsintown after connecting? Refresh the connector to load the Bandsintown tools.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-bandsintown \
  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-bandsintown": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-bandsintown]
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: bandsintown_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: bandsintown_write

How to use the Bandsintown REST API

Create your Cotlet API key

Create a Cotlet API key with access to Bandsintown and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Bandsintown in Cotlet and enable it for agents. Account access: Your own Bandsintown for Artists account, with admin access to the artist page.

Make your first Bandsintown API request

REST:

curl "https://cotlet.dev/api/v1/bandsintown/events?status=all" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read events and apply the operation limits

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": "bandsintown",
  "tool": "list_events",
  "result": {
    "events": [
      {
        "event_id": "1037728455",
        "status": "published",
        "starts_at": "2026-11-14T20:00:00+00:00",
        "venue": {
          "name": "Brudenell Social Club",
          "city": "Leeds",
          "country": "United Kingdom"
        },
        "ticket_links": [
          {
            "url": "https://tickets.example.com/yourband-leeds",
            "type": "tickets"
          }
        ],
        "url": "https://www.bandsintown.com/e/1037728455"
      },
      {
        "event_id": "1037728501",
        "status": "draft",
        "starts_at": "2026-12-03T19:30:00+01:00",
        "venue": {
          "name": "Columbiahalle",
          "city": "Berlin",
          "country": "Germany"
        },
        "ticket_links": [],
        "url": null
      }
    ]
  }
}

Returns events of one artist page, soonest first, with date, venue, ticket links and whether each is published or a draft. Filter by status or by date range.

Use the event_id from each item in the other tools.

from: Only events on or after this date.

to: Only events on or before this date.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Bandsintown workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	One event in full: venue, lineup, description, ticket links, on-sale time and URL. Use `get_event` in your configured content report.
Make	HTTP > Make a request	Total followers, RSVPs and ticket clicks with the change over a period, from Insights. Use `get_follower_stats` in your configured content report.
Python or Node.js	REST API	Locations where your fans are, ranked by trackers or fan requests. Use `get_top_markets` in your configured content report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Bandsintown; 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.

Bandsintown API endpoints and MCP tools

Events, drafts and venues

New events start as drafts no fan sees. A scheduled publish needs at least 4 hours from now and 15 minutes before the show.

List events (list_events, read): Events on your artist page with date, venue, ticket links and status.
Get event (get_event, read): One event in full: venue, lineup, description, ticket links, on-sale time and URL.
Search venues (search_venues, read): Find a Bandsintown venue by name and city, to attach it to an event.
Create event (create_event, write): New event saved as a draft. Nothing is public until you publish it.
Update event (update_event, write, asks first): Change the date, venue, lineup, description or ticket links of a draft or published event.
Publish event (publish_event, write, asks first): Publish a draft now or at a set time, optionally notifying followers.
Delete event (delete_event, write, asks first): Remove an event from your artist page.

Posts to followers

Push and email to followers. One post targets one location at most.

Send fan message (send_fan_message, write, asks first): Post to your followers by push notification and email, now or at a set time.

Insights

The free Insights figures, which fill in once the page has 100 followers.

Get event stats (get_event_stats, read): RSVPs for each of your shows, as in the Events Performance view of Insights.
Get follower stats (get_follower_stats, read): Total followers, RSVPs and ticket clicks with the change over a period, from Insights.
Get top markets (get_top_markets, read): Locations where your fans are, ranked by trackers or fan requests.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/bandsintown-api-mcp-server#tools

Who can see my Bandsintown session, and how do I revoke it?

What we store. Your signed-in Bandsintown for Artists profile, AES-256-GCM, in Finland. Not your password.
What your agent gets. The 11 Bandsintown tools. No cookie, no API key of yours.
What the session sees. Every artist page your login manages, with its events and Insights.
What no tool touches. Paid email campaigns, billing, page admins and account settings.
If Bandsintown signs you out. You get an email with a sign-in link. We never sign in for you.
How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.

Bandsintown's artist terms make you liable for anything done through your profile, including by a third party with your login, so treat the Cloud Browser as a team login you can end in one click. Our site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); no SOC 2 report or third-party pentest yet.

Is it against Bandsintown's terms? Account safety

You shall not use any automated means (e.g., scraping, robots, etc.) other than the Bandsintown Data Applications (in accordance with these Data Applications Terms of Use) to access, query or otherwise collect the Bandsintown Content or any other information or data from the Services.

Bandsintown Data Applications Terms of Use, 3.d, 25 Feb 2019

Those are the terms of the API and widgets, which every artist with a key accepts. The Terms of Use for Artists (14 May 2024) ban screen scraping to collect lists of other users, count managers and booking agents as the artist, and make the artist answer for a third party using the login. Cotlet works in your dashboard as you, which Bandsintown could still call automated access. We found no public case of an artist account closed for it (checked 27 Oct 2026).

How we keep your account looking like you:

Your own Bandsintown for Artists login, signed in by you
One Cloud Browser with its own IP and cookies
Edits, publishing, deletes and posts wait for your OK
No scraping of other artists, fans or venues
If Bandsintown objects, we pause the Bandsintown tools for everyone within 24 h

The artist terms license Insights only for promoting your own shows and bar passing it to Bandsintown's competitors. Keep agent reports inside your team.

What happens when Bandsintown changes?

12 h between tests of the Bandsintown reads and drafts
24 h between tests of publishing and posts fans would see
$0 for a call to a Bandsintown tool paused for repair

When Bandsintown for Artists moves the event form or renames an Insights view, we fix it on our side. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Finds the one show. Date and city from the promoter email; asks if two match.
Reads it in full. Venue, lineup and every ticket link before the edit.
Waits for your OK. New date and the alert choice, in your Cotlet console.
Reads it back. The saved event and whether followers were told.

Action	Undo
Create a draft	delete_event removes it; no fan saw it
Update an event	Change it back; an alert already sent stays sent
Publish an event	No unpublish tool; delete_event takes it off the page
Post to followers	No, a push or email cannot be recalled
Delete an event	No; re-create it from the saved details

4 of 11 tools ask first: every edit, publish, delete and post. create_event runs at once because a draft reaches nobody. You can switch the wait off per tool for a scheduled run.

Bandsintown alerts followers about a change to a published event unless Notify my Followers is off. update_event keeps it off unless you ask for it.

MCP call:

{
  "name": "create_event",
  "arguments": {
    "starts_at": "2026-11-14T20:00:00+00:00",
    "venue_id": "v_118302",
    "ticket_links": [
      {
        "url": "https://tickets.example.com/yourband-leeds",
        "type": "tickets"
      }
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/bandsintown/events \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"starts_at":"2026-11-14T20:00:00+00:00","venue_id":"v_118302","ticket_links":[{"url":"https://tickets.example.com/yourband-leeds","type":"tickets"}]}'

Response:

{
  "event_id": "1037728455",
  "status": "draft",
  "starts_at": "2026-11-14T20:00:00+00:00",
  "venue": {
    "name": "Brudenell Social Club",
    "city": "Leeds",
    "country": "United Kingdom"
  },
  "ticket_links": [
    {
      "url": "https://tickets.example.com/yourband-leeds",
      "type": "tickets"
    }
  ],
  "url": null
}

Scripts reach the same tools over REST at /api/v1/bandsintown, with one key and one price, for a nightly sync from your booking sheet. A call your artist role cannot make fails and costs nothing. Each tool row above shows its REST path.

How much does the Bandsintown MCP server cost?

About $12 a month for a touring band adding one 8-date leg a month, 2,120 credits. Bandsintown for Artists itself stays free.

Job	Calls	Credits
Add an 8-date leg as drafts	17 × 1	170
Publish the leg on announce day	8 × 1	80
Move a date or mark it sold out	3 × 4	120
On-sale post to followers	2 × 4	80
Weekly followers and RSVPs	3 × 4	120
Where to tour next, from top markets	5 × 1	50
Cloud Browser, 30 days		1,500
Total		2,120

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
No API key or partner request needed

The month is our example: about 5,000 followers, one leg of 8 dates, four changes, four on-sale posts and a weekly look at the numbers. Bandsintown publishes no size for a typical artist page. Paid Bandsintown email campaigns are billed by Bandsintown, not by us. Dollars at the $29 pack rate.

Bandsintown MCP server on GitHub, Zapier or hosted: which to use

Option	What it does	Where it stops
pipeworx-io/mcp-bandsintown	Hosted MCP with two tools, artist_events and events, through the Pipeworx gateway.	Public event listings only. 0 stars, last commit 19 Sep 2026.
n8n-nodes-bandsintown	Community n8n node for Artist Information and Artist Events on your API key.	Reads only, like the API under it. 0 stars, last commit 13 Jun 2026.
Apify Bandsintown scrapers	Public concerts, tour dates and ticket links, each also served through Apify's MCP.	Public pages only, about $1 to $15 per 1,000 results.
Upload Events in Bandsintown	Bandsintown's own bulk import from its template spreadsheet.	Retype your sheet into its columns; new events go public within minutes.

Need your dates on your own site? The free API key and widget do that. A gig guide for fans can use Pipeworx or the scrapers. If your agent should also draft, move and publish dates, post to followers and read Insights, that is what Cotlet does.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), founded in 2019 by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the Bandsintown tools.

Bandsintown API and MCP: questions

How do I get access?

Create a free account at https://cotlet.dev, open Bandsintown under Integrations in the console and sign in to Bandsintown for Artists in its Cloud Browser. The trial starts when you sign up and needs no card.

How do I connect Bandsintown to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Bandsintown 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 Bandsintown account through Cotlet, in their phone apps too.

What can ChatGPT do in Bandsintown?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Bandsintown: add tour dates from a spreadsheet; reschedule a show or mark it sold out; mark a show as sold out. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need a Bandsintown API key?

No. Cotlet works through your Bandsintown for Artists account. The official API key is linked to one artist, comes from the artist Settings, and only reads artist info and events.

Do followers get an alert when my agent edits an event?

Only if you ask. Bandsintown notifies followers about event changes unless Notify my Followers is off. update_event keeps notify_followers off by default, and publish_event turns it on by default.

Can one login handle several artists?

Yes. Most tools take an artist_id, so a manager whose login runs several artist pages names the page per call. Without it the tools use the first artist on the login.

Does Bandsintown have webhooks?

Not in its public API docs. Nothing tells an agent that an imported date appeared or RSVPs jumped, so run it on a schedule, for example a weekly pass of list_events and get_event_stats.

Is the MCP server different from the REST API?

Only in how you call it. MCP and REST carry the same 11 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Bandsintown?

No. Cotlet is independent and not affiliated with Bandsintown, LLC.

Can I use the Bandsintown 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.

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.