Eventim MCP server: let your AI agent search concerts and events by city and date

#What your agent gets

The tool takes a query (artist, tour or keyword). It also takes an optional city, date_from, date_to and page. The city and date filters apply to the events the search returns, as a text match on the city. Each event has a name, artist, tour, start time, venue, availability, status, fan-resale flag, rating and event link.

Eventim's search API returns no prices. For prices, your agent sends you to the event page.

#How a request flows

1. You ask your agent: "Find Die Ärzte concerts in Hamburg next year."
2. The agent calls find_recipe, then run with eventim.de/search-events, the query "Die Ärzte" and the city "Hamburg".
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends one search request from an eventim.de tab, so it carries your normal browser session.
5. The events go back to your agent. Nothing passes through wield.run.

Eventim's API rejects requests from servers. The recipe therefore runs only in your browser.

#What leaves your computer

The only host is public-api.eventim.com, and one search makes one request. Buying tickets stays on eventim.de. Wield returns the event link and never opens a checkout, joins a queue or buys anything.

Results stay on your computer. Wield logs each request locally 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.

#Eventim terms, in plain words

We have not reviewed Eventim's terms as a lawyer would, so this is not legal advice. Our reading is that Eventim's terms prohibit automated access to its systems. This recipe runs one search that you start, from your own browser. It never automates queueing or purchase. Check Eventim's terms yourself before you automate anything else.

#Limits and what is not working yet

• Read only. Ticket purchase is not part of the recipe.
• Browser only. Eventim rejects server requests, so the tool works only where your own browser runs.
• No prices. The results have dates, venues and availability, but no prices.
• Filters are applied after the search. City and date limit the events returned, so a broad query can return fewer matches than you expect.
• Preliminary numbers. The benchmark is still running. Its figures are in the FAQ below.

#FAQ

#Is there an official Eventim MCP server?

Not that we know of as of 7 November 2026. Eventim sells tickets in its own shop.

#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.

#Does it need an Eventim login?

No. Search runs without an Eventim account.

#How fast is it compared with a browser agent?

The benchmark task checks for at least three events with a name and date. As of 7 November 2026, and still preliminary, the Wield recipe passed 9 of 9 runs with a median of 286 ms and no model cost. Browser Use with Claude Sonnet 5.5 passed 0 of 9. Bot protection blocked all 9 of its runs, with a median of 120.9 seconds and $0.06 per run. See the Eventim benchmark.