Eventbrite MCP server Let your AI agent run your Eventbrite events.

ToolWhat it doesAccess

• list_events Your events with date, status and tickets sold. read

  Lists the events of your organization as the Events page shows them. Each row carries the event_id the other tools take, the date, the status and the number of tickets sold. Use query to find an event by words from its title.

  MCP calleventbrite_read → list_events

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/events

  Parameters

  Parameters: list_events

  Name	Type	Description
  status string	string	Filter by the status the Events page shows, for example live or draft.
  query string	string	Words from the event title.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "events": [
      {
        "event_id": "812340551",
        "name": "Saturday trail run",
        "starts_at": "2026-11-14T08:00:00-08:00",
        "status": "live",
        "tickets_sold": 120
      },
      {
        "event_id": "812340987",
        "name": "Beginner night swim",
        "starts_at": "2026-11-19T19:00:00-08:00",
        "status": "live",
        "tickets_sold": 41
      }
    ],
    "next_cursor": null
  }

• get_event One event with its venue, dates, status and ticket types. read

  Returns the event as its dashboard shows it: title, summary, start and end, venue, status and each ticket type with its price and the number sold. It changes nothing.

  MCP calleventbrite_read → get_event

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/events/{event_id}

  Parameters

  Parameters: get_event

  Name	Type	Description
  event_id string required	string	Event ID from list_events.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "event_id": "812340551",
    "name": "Saturday trail run",
    "status": "live",
    "starts_at": "2026-11-14T08:00:00-08:00",
    "ends_at": "2026-11-14T11:00:00-08:00",
    "venue": "Pine Ridge trailhead",
    "ticket_types": [
      {
        "name": "General admission",
        "price": "25.00 USD",
        "sold": 120
      },
      {
        "name": "Volunteer",
        "price": "0.00 USD",
        "sold": 8
      }
    ]
  }

• copy_event Copy an event into a new draft with a new title and date. writeasks first

  Runs More, Copy event: a new event with the details of the old one, and the new title, summary and date and time you give. The copy is not published. It uses the payout method of the original event. Waitlist settings, tracking links, emails to attendees, online event pages and attendee details are not copied. By default you confirm each call; you can switch that off for this tool.

  MCP calleventbrite_write → copy_event

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/events/{event_id}/copy

  Parameters

  Parameters: copy_event

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  title string required	string	Title of the new event.
  summary string	string	Summary of the new event. Leave out to keep the old one.
  starts_at string required	string	ISO date and time the new event starts.
  ends_at string required	string	ISO date and time the new event ends.

  Example input

  {
    "event_id": "event_8c41d2",
    "title": "title",
    "starts_at": "starts at",
    "ends_at": "ends at"
  }

  Example response

  {
    "new_event_id": "812341200",
    "copied_from": "812340551",
    "name": "Saturday trail run, December",
    "status": "draft"
  }

• publish_event Publish a draft event now or at a set time. writeasks first

  Publishes the event, now or scheduled, like the Publish button. A published event is visible to the public and can sell tickets. Review the payout method, ticket settings, order form and refund policy first; get_event shows the ticket types. By default you confirm each call; you can switch that off for this tool.

  MCP calleventbrite_write → publish_event

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/events/{event_id}/publish

  Parameters

  Parameters: publish_event

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  publish_at string	string	ISO date and time to publish later. Leave out to publish now.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "event_id": "812341200",
    "status": "live",
    "url": "https://www.eventbrite.com/e/saturday-trail-run-december-tickets-812341200"
  }

ToolWhat it doesAccess

• list_orders Orders across all your events, or for one event. read

  Lists orders from Manage orders, for one event or across all events. Each row has the order_id, the buyer name and email, the total and the order status. Use query to search by buyer name or email. order_type switches between completed orders and refunded or cancelled ones.

  MCP calleventbrite_read → list_orders

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/orders

  Parameters

  Parameters: list_orders

  Name	Type	Description
  event_id string	string	Limit to one event. Leave out for all events.
  query string	string	Buyer name or email.
  order_type string	string	completed for all completed orders, refunded_cancelled for refunded and cancelled orders. Default completed.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "orders": [
      {
        "order_id": "9921043387",
        "event_id": "812340551",
        "buyer": "Jordan Ellis",
        "email": "jordan@example.com",
        "total": "50.00 USD",
        "status": "completed"
      },
      {
        "order_id": "9921043412",
        "event_id": "812340551",
        "buyer": "Priya Nair",
        "email": "priya@example.com",
        "total": "25.00 USD",
        "status": "completed"
      }
    ],
    "next_cursor": null
  }

• get_order One order with its tickets, total and refund state. read

  Returns the order as Manage orders shows it: buyer, each ticket with its type and price, the total and any amount already refunded. Read it before refund_order to see which tickets can still be refunded.

  MCP calleventbrite_read → get_order

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/orders/{order_id}

  Parameters

  Parameters: get_order

  Name	Type	Description
  order_id string required	string	Order ID from list_orders.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "9921043387",
    "event_id": "812340551",
    "buyer": "Jordan Ellis",
    "email": "jordan@example.com",
    "tickets": [
      {
        "attendee_id": "5531002001",
        "type": "General admission",
        "price": "25.00 USD"
      },
      {
        "attendee_id": "5531002002",
        "type": "General admission",
        "price": "25.00 USD"
      }
    ],
    "total": "50.00 USD",
    "refunded": "0.00 USD",
    "status": "completed"
  }

• refund_order Refund an order in full or in part. writeasks first

  Runs Refund this order from Manage orders: you choose the tickets and the amount, and Eventbrite emails the buyer a refund confirmation. The money goes back to the original payment method within 5 to 7 business days. Free orders cannot be refunded; cancel or delete them in Eventbrite. If Eventbrite asks for a card to cover the refund, the call stops with that message and you finish it in Eventbrite. By default you confirm each call; you can switch that off for this tool.

  MCP calleventbrite_write → refund_order

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/orders/{order_id}/refund

  Parameters

  Parameters: refund_order

  Name	Type	Description
  order_id string required	string	Order ID from list_orders.
  attendee_ids array	array	Tickets to refund, from get_order. Leave out to refund the whole order.
  amount string	string	Amount to refund, for example 25.00. Leave out for the full price of the chosen tickets.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "9921043387",
    "status": "refunded",
    "refunded": "50.00 USD",
    "buyer_notified": true
  }

ToolWhat it doesAccess

• list_attendees Attendees of one event with ticket type and check-in status. read

  Lists the attendees from the event dashboard under Manage attendees. Each row has the attendee_id, the order_id, the name and email on the order, the ticket type and whether the attendee is checked in. Filter by ticket type or check-in status, or search by the name or email on the order.

  MCP calleventbrite_read → list_attendees

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/events/{event_id}/attendees

  Parameters

  Parameters: list_attendees

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  ticket_type string	string	Ticket type name as shown in get_event.
  checked_in boolean	boolean	true for checked-in attendees, false for the rest. Leave out for all.
  query string	string	Name or email on the order.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "attendees": [
      {
        "attendee_id": "5531002001",
        "order_id": "9921043387",
        "name": "Jordan Ellis",
        "email": "jordan@example.com",
        "ticket_type": "General admission",
        "checked_in": false
      },
      {
        "attendee_id": "5531002003",
        "order_id": "9921043412",
        "name": "Priya Nair",
        "email": "priya@example.com",
        "ticket_type": "General admission",
        "checked_in": true
      }
    ],
    "next_cursor": null
  }

• check_in_attendee Check attendees in, or check them out again. write

  Does what the Check-in page does: ticks the attendees you name as checked in, or checks them out when checked_in is false. Several attendees go in one call. A check-in reaches no one and is undone with the same call set to false, so it does not wait for your OK.

  MCP calleventbrite_write → check_in_attendee

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/events/{event_id}/attendee/check

  Parameters

  Parameters: check_in_attendee

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  attendee_ids array required	array	Attendee IDs from list_attendees.
  checked_in boolean	boolean	true to check in, false to check out. Default true.

  Example input

  {
    "event_id": "event_8c41d2",
    "attendee_ids": "attendee ids"
  }

  Example response

  {
    "event_id": "812340551",
    "updated": [
      {
        "attendee_id": "5531002001",
        "checked_in": true
      }
    ]
  }

• email_attendees Send or schedule an email to the attendees of one event. writeasks first

  Creates an email under Emails to attendees. send_to picks all attendees, attendees who registered after a date, specific attendees or one ticket type. "All attendees" reaches only people registered at the moment it is sent; attendees who have not registered yet or whose orders were cancelled get nothing. Leave send_at out to send now. send_test sends one test email and nothing else. For a recurring event you can only send now or at one date and time. If your login lacks the permission to email attendees, the call fails and says the account owner must grant it. By default you confirm each call; you can switch that off for this tool.

  MCP calleventbrite_write → email_attendees

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/events/{event_id}/attendees/email

  Parameters

  Parameters: email_attendees

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  subject string required	string	Email subject.
  body string required	string	Email text.
  send_to string required	string	all, registered_after, specific_attendees or ticket_type.
  registered_after string	string	ISO date. Needed when send_to is registered_after.
  attendee_ids array	array	Attendee IDs from list_attendees. Needed when send_to is specific_attendees.
  ticket_type string	string	Ticket type name. Needed when send_to is ticket_type.
  reply_to string	string	Address that gets the replies.
  send_at string	string	ISO date and time to send later. Leave out to send now.
  send_test boolean	boolean	true to send only a test email to your own address.

  Example input

  {
    "event_id": "event_8c41d2",
    "subject": "subject",
    "body": "body",
    "send_to": "send to"
  }

  Example response

  {
    "event_id": "812340551",
    "status": "sent",
    "send_to": "all",
    "recipients": 128
  }

ToolWhat it doesAccess

• get_sales_audit_report Tickets sold and net sales for one event, per ticket type. read

  Reads the Audit report under Sales in Event reports: the total tickets sold at face value, which Eventbrite calls net sales, split by ticket type. Your Eventbrite role needs permission to view Advanced reports, otherwise the call fails and says so. It changes nothing.

  MCP calleventbrite_read → get_sales_audit_report

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/events/{event_id}/sales-audit-report

  Parameters

  Parameters: get_sales_audit_report

  Name	Type	Description
  event_id string required	string	Event ID from list_events.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "event_id": "812340551",
    "rows": [
      {
        "ticket_type": "General admission",
        "tickets_sold": 120,
        "net_sales": "3000.00 USD"
      },
      {
        "ticket_type": "Volunteer",
        "tickets_sold": 8,
        "net_sales": "0.00 USD"
      }
    ],
    "total": {
      "tickets_sold": 128,
      "net_sales": "3000.00 USD"
    }
  }

• create_promo_code Add a discount or access code to one event. writeasks first

  Adds a code under Promotions in the event's Tickets, with the settings the form has: code name, ticket limit, a set amount or a percentage off, start and end dates, and which tickets it applies to. reveal_hidden_tickets makes the code an access code for tickets that are hidden. By default the code is available as long as the tickets it applies to are available. A live code gives buyers a price cut, so it counts as money. By default you confirm each call; you can switch that off for this tool.

  MCP calleventbrite_write → create_promo_code

  REST endpointPOST https://cotlet.dev/api/v1/eventbrite/events/{event_id}/promo-codes

  Parameters

  Parameters: create_promo_code

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  code string required	string	The code buyers enter at checkout.
  percent_off number	number	Percentage taken off. Use this or amount_off.
  amount_off string	string	Fixed amount taken off, for example 5.00. Use this or percent_off.
  ticket_limit integer	integer	How many tickets the code can be applied to.
  starts_at string	string	ISO date and time the code starts.
  ends_at string	string	ISO date and time the code ends.
  ticket_types array	array	Ticket type names the code applies to. Leave out for all applicable tickets.
  reveal_hidden_tickets boolean	boolean	true to reveal hidden tickets at checkout. Default false.

  Example input

  {
    "event_id": "812340551",
    "code": "RUNCLUB15",
    "percent_off": 15,
    "ticket_limit": 40,
    "ends_at": "2026-11-13T23:59:00-08:00"
  }

  Example response

  {
    "event_id": "812340551",
    "code": "RUNCLUB15",
    "percent_off": 15,
    "ticket_limit": 40,
    "applies_to": "all applicable tickets",
    "status": "active"
  }

• search_public_events Public events on Eventbrite for a search phrase and place. read

  Reads the public search results a visitor sees on eventbrite.com: name, date, venue, organizer, price label and link. It needs no events of your own. It returns nothing about orders or attendees. Eventbrite shut down its own search API on 12 Dec 2019, so this is the way to search from an agent.

  MCP calleventbrite_read → search_public_events

  REST endpointGET https://cotlet.dev/api/v1/eventbrite/public-events/search

  Parameters

  Parameters: search_public_events

  Name	Type	Description
  query string required	string	What to search for, for example trail running.
  location string	string	City or area. Leave out for the place Eventbrite picks for your login.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "events": [
      {
        "event_id": "700114820",
        "name": "Sunrise 10K trail race",
        "starts_at": "2026-11-21T07:30:00-08:00",
        "venue": "Cedar Park",
        "organizer": "Valley Runners",
        "price": "From 30.00 USD",
        "url": "https://www.eventbrite.com/e/sunrise-10k-trail-race-tickets-700114820"
      }
    ],
    "next_cursor": null
  }