Bandsintown MCP Server

Bandsintownのアーティストページのツアー日程、ファンからのメッセージ、統計情報。

ホスト型 MCP サーバー

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

Claude Code、Codex、Cursor などにインストールできます

ドキュメント

Cotlet · All integrations · MCP servers · APIs · API & MCP status · How it works · Security · Custom API · 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 Build your own endpoint

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Bandsintown. Bandsintown is a trademark of its owner. If Bandsintown's own integrations cover what you need, use them first.

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 needPublic APIBandsintown ChatGPT appCotlet
List your upcoming and past eventsYes, published onlyPublic listingsYes, drafts too
Add, edit or delete eventsNoNoYes, edits after your OK
Post to followersNoNoYes, after your OK
Top markets, RSVPs, follower trendFollower count onlyNoYes, from Insights
What you set upAPI key from SettingsFan side onlyYour 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?

  1. Sign in to Bandsintown. Use your own account in its Cotlet Cloud Browser.
  2. Connect your agent. Add Cotlet over MCP, or build your own endpoint with Custom API.
  3. Run your workflow. Ask your agent, or call your endpoint over HTTP.

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. For HTTP calls from n8n, Make, Zapier or scripts, build your own endpoint with Custom API, below the MCP setup.

Step by step with screenshots for ChatGPT, Claude, Grok and other agents: How to connect Bandsintown to AI agents and automate the busywork.

  1. Enable Bandsintown for agents. Sign up, sign in to Bandsintown for Artists in its Cloud Browser and press Enable for agents.
  2. Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector settings of your agent.
  3. 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

Need an HTTP endpoint for your Bandsintown account?

Cotlet has no ready REST endpoints for Bandsintown. With Custom API, your AI does a Bandsintown job once in your Cloud Browser, signed in to your own account, and saves it as your own endpoint: POST https://cotlet.dev/api/v1/custom/{name} with your API key, JSON in and JSON out.

Writes wait for your consent after a dry run. For events, such as a new record appearing, use an automation instead. How Custom API works.

Bandsintown MCP tools and operations

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, MCP call 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.

Our site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Finds the one show. Date and city from the promoter email; asks if two match.
  2. Reads it in full. Venue, lineup and every ticket link before the edit.
  3. Waits for your OK. New date and the alert choice, in your Cotlet console.
  4. Reads it back. The saved event and whether followers were told.
ActionUndo
Create a draftdelete_event removes it; no fan saw it
Update an eventChange it back; an alert already sent stays sent
Publish an eventNo unpublish tool; delete_event takes it off the page
Post to followersNo, a push or email cannot be recalled
Delete an eventNo; 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"
      }
    ]
  }
}

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
}

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.

JobCallsCredits
Add an 8-date leg as drafts17 × 1170
Publish the leg on announce day8 × 180
Move a date or mark it sold out3 × 4120
On-sale post to followers2 × 480
Weekly followers and RSVPs3 × 4120
Where to tour next, from top markets5 × 150
Cloud Browser, 30 days1,500
Total2,120
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser

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

OptionWhat it doesWhere it stops
pipeworx-io/mcp-bandsintownHosted 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-bandsintownCommunity 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 scrapersPublic 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 BandsintownBandsintown'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 Cotlet affiliated with Bandsintown?

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

Is there a REST endpoint for Bandsintown?

Not a ready one. Build your own with Cotlet Custom API: your AI does the Bandsintown job once in your Cloud Browser and saves it as an endpoint you call with POST and your API key.


Give your AI agents your signed-in browser.

Product: Integrations · MCP servers · APIs · API & MCP status · How it works · Pricing · Security · Custom API

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.