Sign inTry it

Let Claude search Eventim concerts and events by city and date

To let Claude find concerts and events, install Wield and name an artist, a tour or a keyword. Add a city or a date range if you have one. For example: "Find concerts in Hamburg between 1 and 31 March and list artist, venue and date." Claude runs the eventim.de/search-events recipe in your own browser. It returns matching events with venue, date and ticket availability. No login is needed.

Updated

Live recipeeventim.de/search-eventsv1

Eventim Search concerts and events with dates, venues and ticket availability

Read-only, no loginRuns in your browser only

Parameters (5)
citystringOnly events in this city (text match, e.g. 'Köln', 'Hamburg')
date_fromstringOnly events on or after this date
date_tostringOnly events on or before this date
pageinteger
querystringrequiredArtist, tour, show or keyword, e.g. 'Die Ärzte', 'Coldplay', 'Disney on Ice'
Use it with your agent
Measured on the live site
MetricWield recipeBrowser Use + Claude Sonnet 5.5
Success100%0%
Median time286 ms121 s
Cost per run$0$0.065

9 runs each, 7 November 2026. How we measure

What you need

  • Claude Desktop, Claude Code, Cursor, Codex or another MCP client.
  • A Chromium browser (Chrome, Edge, Brave, Arc, Vivaldi, Opera) with the Wield extension.
  • wield-mcp. Run npx -y wield-mcp init, or use the one-click Claude Desktop bundle on wield.run/install.

For the full setup, follow the quick start.

Ask your agent

Name the artist, tour or keyword. Add the city and the dates if they matter. Claude calls find_recipe to find the recipe, then run with the parameters.

You: Find concerts in Hamburg between 1 and 31 March and list artist, venue and date.

Claude then runs eventim.de/search-events with query, city, date_from and date_to.

Params: what to put where

ParamRequiredWhat to put in it
queryyesArtist, tour, show or keyword, for example Die Ärzte, Coldplay or Disney on Ice.
citynoOnly events in this city. It is a text match, for example Köln or Hamburg.
date_fromnoOnly events on or after this date.
date_tonoOnly events on or before this date.
pagenoResults page. Default 1.

The city and date filters apply to the events the search returns. They do not change Eventim's own query.

What comes back

The result has query, total_groups, tours and events. total_groups is the number of matching artists or tours on Eventim. Each tour shows its date range and number of events.

Each event shows the event name, artist, tour, start date and time, venue, city, zip, ticket availability, status, the resale flag, the rating and rating count, and the event page URL. This recipe returns no prices. For prices and tickets, open the event page on eventim.de.

What leaves your computer

The recipe makes 1 request to public-api.eventim.com. It goes out from an eventim.de tab in your browser. Nothing passes through wield.run. Eventim's bot protection rejects requests from non-browser clients, so the recipe runs only in your browser.

Limits and terms

  • Eventim's terms prohibit automated access to its systems. The recipe runs one search at a time from your browser. Buying tickets stays on eventim.de. Never automate queueing or purchase.
  • Status on 7 Nov 2026 is "ok". The check ran 4 verify checks, found 16 to 18 groups, and used 1 request.

In our benchmark (as of 7 Nov 2026, preliminary, still running), the recipe passed 9 of 9 runs with a median of 286 ms and no model cost. In our runs, Eventim's bot protection blocked Browser Use with Claude Sonnet 5.5 in all 9 runs. It passed 0 of 9, with a median of 120.9 s and $0.06 per run. The check required at least three events with name and date. The method is on the benchmark page.

FAQ

Can Claude buy tickets?

No. The recipe only searches. Queueing and purchase stay on eventim.de.

Does it show ticket prices?

No. In our check, the Eventim API returns no prices. Open the event page to see them.

Does it need a login?

No. The search needs no login.

Is there an official Eventim MCP server?

Not that we know of as of 7 November 2026.

How fast is it compared with a browser agent?

In our preliminary benchmark, the recipe's median was 286 ms. The browser agent's median was 120.9 s, and bot protection blocked it in every run. Full details are on the benchmark page.