# Bandsintown API and MCP server

> Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026). You cannot add, edit or delete events, post to followers or read Insights through it, and each API key is tied to one artist.

Concert discovery app where fans follow artists and get alerts for shows; artists and managers run their page in Bandsintown for Artists: events, ticket links, posts to followers and Insights.

## What is the Bandsintown API?

Cotlet's Bandsintown API exposes 11 endpoints for your own Bandsintown account: list events, get event, search venues, get event stats, get follower stats, get top markets, create event, update event, publish event, delete event and send fan message. The list_events endpoint returns events on your artist page with date, venue, ticket links and status. Each endpoint takes simple JSON inputs like artist_id, event_id or notify_followers and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-11

Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Bandsintown with 11 endpoints (6 read, 5 write): your AI agent signs in as you and does the work.

## Does Bandsintown have an official API?

Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026). You cannot add, edit or delete events, post to followers or read Insights through it, and each API key is tied to one artist.

| Task | Bandsintown official | Cotlet |
|---|---|---|
| List upcoming and past events | Yes: Artist events request: upcoming, past, all or a date range | Yes |
| Add an event with venue and ticket links | No | Yes |
| Edit or delete events | No | Yes |
| Save drafts and schedule publishing | No | Yes |
| Post to followers | No | Yes |
| Read follower, RSVP and ticket click totals | No | Yes |
| Read top markets | No | Yes |

Sources: [Bandsintown help: API documentation](https://help.artists.bandsintown.com/en/articles/9186477-api-documentation), [Bandsintown help: What is the Bandsintown API?](https://help.artists.bandsintown.com/en/articles/7053475-what-is-the-bandsintown-api), [Bandsintown help: Add an event](https://help.artists.bandsintown.com/en/articles/7039442-add-an-event), [Bandsintown for Artists: Insights](https://www.artists.bandsintown.com/support/insights), [Bandsintown help: Add multiple events at once](https://help.artists.bandsintown.com/en/articles/7170746-add-multiple-events-at-once), [Bandsintown help: Edit events](https://help.artists.bandsintown.com/en/articles/7170758-edit-events), [Bandsintown help: Manage email notifications](https://help.artists.bandsintown.com/en/articles/7039360-manage-email-notifications)

## For AI agents

```text
Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026). You cannot add, edit or delete events, post to followers or read Insights through it, and each API key is tied to one artist.
Cotlet provides a hosted MCP server and REST API for Bandsintown: 11 tools (6 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=bandsintown; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/bandsintown
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_events, get_event, search_venues, get_event_stats, get_follower_stats, get_top_markets, create_event, update_event, publish_event, delete_event, send_fan_message
Confirm      update_event, publish_event, delete_event, send_fan_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/bandsintown-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=bandsintown (Bandsintown is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Bandsintown once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Bandsintown server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Bandsintown in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Bandsintown's terms; Cotlet is not affiliated with Bandsintown.
```

## What can an AI agent do in Bandsintown?

Cotlet is best for artists and managers who keep their tour on Bandsintown and want an AI agent to add and change dates, post to followers and report Insights without running or fixing a server.

- **[Add tour dates from a spreadsheet](https://cotlet.dev/integrations/bandsintown-api-mcp-server/add-tour-dates-from-spreadsheet)**: "Add the 12 dates in tour.csv to our Bandsintown page as drafts with their ticket links. Skip any show Bandsintown already imported from Ticketmaster or the venue, and list the venues you could not match." → `list_events`, `search_venues`, `create_event`
- **[Reschedule a show or mark it sold out](https://cotlet.dev/integrations/bandsintown-api-mcp-server/reschedule-show)**: "The Leeds show moved from 14 Nov to 21 Nov at the same venue, and Berlin on 3 Dec just sold out. Update both on Bandsintown and do not notify followers about the sold out change." → `list_events`, `get_event`, `update_event`, `delete_event`
- **Mark a show as sold out**: "Mark the Berlin show as sold out on Bandsintown." → `list_events`, `update_event`
- **Post to followers when tickets go on sale**: "Post to our followers on Friday at 10:00 that tickets for the 14 Nov Leeds show are on sale, with the smart link." → `list_events`, `send_fan_message`
- **[Find cities to tour from fan requests and top markets](https://cotlet.dev/integrations/bandsintown-api-mcp-server/find-cities-to-tour-from-fan-requests)** (runs: monthly): "Compare our Bandsintown top markets and fan requests with the tour we have booked. Which cities have demand but no date, and which booked shows have few RSVPs?" → `get_top_markets`, `list_events`, `get_event_stats`, `get_follower_stats`

## Can Bandsintown automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Bandsintown connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to find cities to tour from fan requests and top markets, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/bandsintown/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/bandsintown/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/bandsintown/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/bandsintown/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Bandsintown.

### list_events

Events on your artist page with date, venue, ticket links and status. Access: read. REST: `POST /api/v1/bandsintown/list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `status` | enum | no | upcoming, past, draft or all. Default: upcoming. |
| `from` | date | no | Only events on or after this date. |
| `to` | date | no | Only events on or before this date. |

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.

Example response:

```json
{
  "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
    }
  ]
}
```

### get_event

One event in full: venue, lineup, description, ticket links, on-sale time and URL. Access: read. REST: `POST /api/v1/bandsintown/get_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Returns one event with every field you can set in the event form: location, lineup, description and ticket links with their on-sale time. Bandsintown rewrites ticket links, so the links shown are the ones you entered.

Example response:

```json
{
  "event_id": "1037728455",
  "status": "published",
  "starts_at": "2026-11-14T20:00:00+00:00",
  "venue": {
    "name": "Brudenell Social Club",
    "city": "Leeds",
    "country": "United Kingdom"
  },
  "lineup": [
    "Your Band"
  ],
  "description": "Album launch show.",
  "ticket_links": [
    {
      "url": "https://tickets.example.com/yourband-leeds",
      "type": "tickets",
      "on_sale_at": "2026-10-16T10:00:00+01:00"
    }
  ],
  "url": "https://www.bandsintown.com/e/1037728455"
}
```

### search_venues

Find a Bandsintown venue by name and city, to attach it to an event. Access: read. REST: `POST /api/v1/bandsintown/search_venues`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Venue name. |
| `city` | string | no | City, to narrow the results. |

Searches the Bandsintown venue list and returns matches with a venue_id. If the venue is not listed, pass custom_location to create_event instead. Attach a venue with a full location: events without one are not considered by Bandsintown's recommendations.

Example response:

```json
{
  "venues": [
    {
      "venue_id": "v_118302",
      "name": "Brudenell Social Club",
      "city": "Leeds",
      "country": "United Kingdom"
    }
  ]
}
```

### get_event_stats

RSVPs for each of your shows, as in the Events Performance view of Insights. Access: read. REST: `POST /api/v1/bandsintown/get_event_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `event_id` | string | no | Only this event. Default: all upcoming events. |

Returns RSVPs per show from Insights, the same figures as Events Performance. Pass event_id for one show, or leave it out for all upcoming shows.

Example response:

```json
{
  "events": [
    {
      "event_id": "1037728455",
      "venue": "Brudenell Social Club",
      "starts_at": "2026-11-14T20:00:00+00:00",
      "rsvps": 212
    }
  ]
}
```

### get_follower_stats

Total followers, RSVPs and ticket clicks with the change over a period, from Insights. Access: read. REST: `POST /api/v1/bandsintown/get_follower_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `period` | enum | no | 7d, 4w or 12m. Default: 4w. |

Returns the Insights summary: total followers, RSVPs and ticket clicks, with how much each changed in the period. Periods match the Insights filters. Read only.

Example response:

```json
{
  "period": "7d",
  "followers": {
    "total": 18420,
    "change": 163
  },
  "rsvps": {
    "total": 2310,
    "change": 54
  },
  "ticket_clicks": {
    "total": 1190,
    "change": 37
  }
}
```

### get_top_markets

Locations where your fans are, ranked by trackers or fan requests. Access: read. REST: `POST /api/v1/bandsintown/get_top_markets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `rank_by` | enum | no | trackers or fan_requests. Default: trackers. |
| `limit` | integer | no | 1 to 50. Default: 10. |

Returns your top locations from Insights, the same list as Top Markets. Sort by trackers (followers) or by fan requests (fans asking you to play there). Read only.

Example response:

```json
{
  "markets": [
    {
      "rank": 1,
      "location": "London, United Kingdom",
      "trackers": 2104,
      "fan_requests": 311
    },
    {
      "rank": 2,
      "location": "Leeds, United Kingdom",
      "trackers": 1388,
      "fan_requests": 96
    }
  ]
}
```

### create_event

New event saved as a draft. Nothing is public until you publish it. Access: write. REST: `POST /api/v1/bandsintown/create_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `starts_at` | datetime | yes | Local venue time, ISO 8601. |
| `venue_id` | string | no | Venue from search_venues. Or use custom_location. |
| `custom_location` | object | no | name, city, country, for a place not in the venue list. |
| `title` | string | no | Event name, if different from the artist name. |
| `description` | string | no | Event description. |
| `lineup` | string[] | no | Other artists with a Bandsintown page on the bill. |
| `ticket_links` | object[] | no | List of { url, type, on_sale_at }; type is tickets, free or sold_out. One link must be tickets. |

Saves a new event as a draft; Bandsintown lists drafts under Drafts. Attach a venue from search_venues or pass custom_location. One ticket link must carry the Tickets label. create_event reaches no one and one delete_event call undoes it, so it runs without asking first.

Example response:

```json
{
  "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
}
```

### update_event

Change the date, venue, lineup, description or ticket links of a draft or published event. Access: write, asks the user first. REST: `POST /api/v1/bandsintown/update_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `fields` | object | yes | Any of starts_at, venue_id, custom_location, title, description, lineup, ticket_links. |
| `notify_followers` | boolean | no | Alert followers about the change. Default: false. |

Changes only the fields you pass, on a published event or a draft. Bandsintown notifies followers of changes unless Notify my Followers is off; notify_followers defaults to false here, so set it to true only for changes fans must hear about, such as a new venue. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "1037728455",
  "status": "published",
  "starts_at": "2026-11-21T20:00:00+00:00",
  "ticket_links": [
    {
      "url": "https://tickets.example.com/yourband-leeds",
      "type": "tickets"
    }
  ],
  "followers_notified": false
}
```

### publish_event

Publish a draft now or at a set time, optionally notifying followers. Access: write, asks the user first. REST: `POST /api/v1/bandsintown/publish_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `publish_at` | datetime | no | Schedule for later. Default: now. |
| `notify_followers` | boolean | no | Alert followers. Default: true. |

Publishes a draft now, or schedules it, as the dashboard's Publish and Schedule to Publish do. With notify_followers on, Bandsintown alerts followers. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "1037728501",
  "status": "scheduled",
  "publish_at": "2026-10-16T10:00:00+01:00",
  "followers_notified": true
}
```

### delete_event

Remove an event from your artist page. Access: write, asks the user first. REST: `POST /api/v1/bandsintown/delete_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |

Deletes one event from your artist page, as the red X on the Events page does. It cannot be undone with a tool, so you re-create the event if needed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "1037728501",
  "status": "deleted"
}
```

### send_fan_message

Post to your followers by push notification and email, now or at a set time. Access: write, asks the user first. REST: `POST /api/v1/bandsintown/send_fan_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `artist_id` | string | no | Artist page you manage. Default: your first artist. |
| `body` | string | yes | Post text. Include your Smart Link. |
| `send_at` | datetime | no | Schedule for later. Default: now. |

Sends a Bandsintown post to your followers: push notification to fans who have enabled it, and email. Send now or schedule with send_at. Add your Smart Link so fans can find your shows. Your latest non-targeted post shows at the top of your artist page. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "msg_20418",
  "status": "scheduled",
  "send_at": "2026-10-16T10:00:00+01:00"
}
```

## How do I connect Bandsintown to Claude Code, Codex or Cursor?

Connecting Bandsintown takes three steps: request access, sign in to Bandsintown once, then add one MCP server or call the REST API with the same key.

### Connect Bandsintown to your agent.

1. **Create an account** Sign up and add Bandsintown in the console. Your API key is there too.

2. **Sign in to Bandsintown once** Open the connect page from the console and sign in to Bandsintown the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Bandsintown tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Add the 12 dates in tour.csv to our Bandsintown page as drafts with their ticket links. Skip any show Bandsintown already imported from Ticketmaster or the venue, and list the venues you could not match.
```

### Call Bandsintown from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/bandsintown/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/bandsintown/create_event \
  -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"}]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "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
}
```

## Why use Cotlet for Bandsintown?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Bandsintown yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Bandsintown changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Bandsintown MCP server on GitHub?

No open-source MCP server or Zapier app for Bandsintown turned up. Most people add and change dates by hand in the Bandsintown for Artists dashboard, one event at a time, and the official API only reads. Cotlet lets your agent do that dashboard work.

|  | By hand in the dashboard | Cotlet |
|---|---|---|
| Setup | None, you use the dashboard | Request access, sign in to Bandsintown once, add one MCP server or API key |
| Adding a tour | Fill in the event form for each date | Your agent reads a spreadsheet and saves each date as a draft |
| When a date or link changes | Open each event and edit it | Your agent updates the events you name |
| Your Bandsintown session | Your browser | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | You sign in again | If Bandsintown logs you out, your agent gets a link to sign in again |
| Where it runs | Your browser, while you work | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Bandsintown changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Bandsintown API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Bandsintown API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Bandsintown account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Bandsintown yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Bandsintown tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Bandsintown in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Bandsintown's terms:** You use your own Bandsintown account and stay responsible for following Bandsintown's terms. Cotlet is independent and not affiliated with Bandsintown. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Bandsintown. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Bandsintown once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Bandsintown session would leave my computer.**

Cotlet keeps your Bandsintown session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**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 my agent post or send messages in Bandsintown without asking me?**

No. Every call to update_event, publish_event, delete_event or send_fan_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_event runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Bandsintown API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/bandsintown/{tool} from the HTTP Request node.