Sign inTry it

Eventbrite MCP server: let your AI agent find events in a city

Wield is an MCP server that gives your AI agent one Eventbrite search tool per site: eventbrite.de for Germany, Austria and Switzerland, eventbrite.com for the US, and eventbrite.co.uk for the UK and Ireland. The tool lists events in a city for a keyword, with an optional date range. Each event shows dates, venue, address and link. The search runs in your own browser, and no model runs inside the recipe.

Updated

Live recipeeventbrite.de/search-eventsv2

Eventbrite Find events in a city on Eventbrite

Read-only, no loginPasses the daily check

Parameters (6)
citystringrequiredCity as named in German, e.g. 'Berlin', 'München', 'Köln', 'Wien', 'Zürich'
countrystring "germany" | "austria" | "switzerland"
date_fromstringEarliest event day, YYYY-MM-DD
date_tostringLatest event day, YYYY-MM-DD (use with date_from)
pageinteger20 events per page
querystringKeyword or category, e.g. 'jazz', 'comedy', 'yoga', 'startup'; 'events' for everything
Use it with your agent

What your agent gets

RecipeWhat it doesLoginStatus (7 Nov 2026)
eventbrite.de/search-eventsLists events in a city by keyword and date range, with venue, address and linksNoOK, 5 of 5 checks, 1 request

The tool takes a required city, written as its German name, such as Berlin, München, Köln, Wien or Zürich. The optional inputs are country (germany, austria or switzerland, default germany), query (default events), date_from, date_to and page. Dates use the form YYYY-MM-DD, and date_to works together with date_from. Each page holds 20 events.

Each event has a name, description, start_date, end_date, online flag, venue, street, postcode, locality, country, coordinates, image, url and matches_query. The result also has matching, the number of events on the page that match every word of your query.

Countries

Wield has one search recipe for each Eventbrite site below. All three return the same event fields and need no login. The inputs differ by site: eventbrite.de takes a German city name and a country (Germany, Austria or Switzerland), eventbrite.com takes a state and a city, and eventbrite.co.uk takes a city and a country (United Kingdom or Ireland). The terms note is the same for all three (see Eventbrite's terms below).

StoreRecipeLoginNotes
Eventbrite.de (Germany, Austria, Switzerland)eventbrite.de/search-eventsNoCity names are German, such as Berlin, München, Wien or Zürich. country defaults to germany. Checked 7 Nov 2026: 5 of 5 checks.
Eventbrite.com (US)eventbrite.com/search-eventsNoTakes a state and a city, for example NY and New York. Checked 7 Nov 2026: 5 of 5 checks.
Eventbrite.co.uk (UK and Ireland)eventbrite.co.uk/search-eventsNocountry is united-kingdom (default) or ireland. Checked 7 Nov 2026: 5 of 5 checks.

How a request flows

  1. You ask your agent: "Find jazz events in Berlin on the first weekend of December 2026."
  2. The agent calls find_recipe, then run with eventbrite.de/search-events, city set to Berlin, query set to jazz, and the two dates.
  3. wield-mcp passes the run through the local bridge to the Wield extension.
  4. The extension sends the request from an eventbrite.de tab in your browser, so it runs as your browser would run the search.
  5. The events go back to your agent. Nothing passes through wield.run.

In our check on 7 November 2026, a Berlin search for jazz passed all 5 checks in one request. Promoted events are left out of the results.

What leaves your computer

A search makes one request to the Eventbrite site you search, such as www.eventbrite.de, for one results page, as the site serves it to a visitor. The recipe does not register you for events and does not buy tickets. Wield logs the request on your computer only, with method, host, path, status and timing, and never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.

Eventbrite's terms, in plain words

We have not reviewed Eventbrite's terms for automated access yet, so this is not legal advice. Eventbrite's robots.txt allows /d/ pages, which are the event list pages the recipe reads. The recipe makes one request for one results page, as the site serves it, for one person's search. Registration and tickets stay on Eventbrite. Check Eventbrite's terms yourself before you run this recipe in any wider way.

Limits and what is not working yet

  • Read only. The recipe lists events. Registration and tickets stay on Eventbrite.
  • The keyword only ranks results. Eventbrite fills the page with other events when few match. Check matches_query on each event. In our check, a nonsense keyword returned the same 3,218 Berlin events as jazz, and it matched none of the first 20.
  • No start times or prices in the search. The event page has them. Open the event's url for both.
  • City names are German. Use München, not Munich, and Wien, not Vienna.
  • Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.

FAQ

Which Eventbrite countries work?

Three country sites have a search recipe: eventbrite.de (Germany, Austria and Switzerland), eventbrite.com (US) and eventbrite.co.uk (UK and Ireland). The Countries table above gives each recipe id. None needs a login.

Does the search show start times and prices?

No. The search results have dates but no start times and no prices. Open the event's url for both.

Can the agent register or buy tickets?

No. The recipe only searches. Open the event's url to register or buy on Eventbrite.

Does it need an Eventbrite login?

No. Search works without an account.

Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config.

How do I know a result really matches my keyword?

Look at matches_query and matching. Eventbrite can show other events on the same page, and each one is marked.