concerts-paris-mcp

A free, public MCP server for searching concerts at the Philharmonie de Paris and the Cité de la musique.

The venue publishes a fine agenda. Its filters are just hard to use for the questions people actually have: baroque, on a weeknight, under 30 euros, still available. This server answers those, then sends you to the official page to book.

Not affiliated. This is an independent project. It is not endorsed by or connected to the Cité de la musique – Philharmonie de Paris. All programme data belongs to them. Tickets are sold only on their site.

Use it

Add the URL to any MCP client that supports remote servers over Streamable HTTP. No account, no API key, no cost.

https://concerts-paris-mcp.samuelbagattin.com/mcp

Tools

Tool	What it does
search_concerts	Free text plus genre, event type, venue, date range, time of day, price ceiling and remaining availability.
get_concert	One programme: every date it is performed, the full cast, prices, current availability. Can re-check availability live.
list_filters	The controlled vocabulary, so a model can pick valid values instead of guessing.
catalogue_status	How complete and how fresh the index is. Worth calling before concluding something does not exist.

What you get back

Facts, and a link. Date and time in Paris, venue, price range, cast, and one of three availability levels: available, few seats left, sold out. There is no seat count anywhere, because the source does not publish one. Every result states when availability was last checked.

What it deliberately does not do

• No programme notes. The venue's editorial text is indexed so that search works, and is never returned. You get facts and a link to the page that has the prose.
• No images. Not copied, not hotlinked.
• No booking. It cannot reserve, hold or pay for anything.
• No money. No ads, no affiliate links, no data resale, no paid tier.

How it reads the source

The venue has no public API, so the catalogue is built from the same endpoints its own agenda page calls. That earns some obligations, and they are enforced in code rather than promised in a README:

• One request per minute at most, from a single process, with a hard 20-second floor between requests on top of that. A full daily refresh is a few hundred requests, roughly one every four minutes.
• An honest User-Agent, naming this project, its URL and a monitored contact address. The server refuses to start collecting if that address is not configured.
• robots.txt fetched, cached briefly and re-checked before every single request. If it ever disallows these paths, collection stops on its own.
• Exponential backoff, Retry-After honoured to the second, and a circuit breaker that also trips when responses get slow, on the view that a struggling origin is asking to be left alone.
• No evasion of any kind. No IP rotation, no User-Agent spoofing, no working around a block. If the source says stop, it stops.

Those rules are covered by tests in src/source/client.test.ts. If one of them starts failing, the project is no longer doing what this page says it does.

The legal reasoning behind all of it, including the text and data mining exception it relies on, is written up in docs/LEGAL.md.

Takedown

If you represent the venue and want this switched off, write to the address on the landing page. It will be taken down within 72 hours, no questions asked.

Develop

npm install
cp .dev.vars.example .dev.vars   # put a real address in CONTACT_EMAIL
npm run db:migrate:local
npm run dev

npm test        # 114 unit tests, no network
npm run check   # tsc

Test fixtures are synthetic. They reproduce the shape of the upstream markup, including its awkward corners, without committing any of the venue's own text to this repository.

Deploy your own

npx wrangler d1 create concerts-paris

Put the returned id in wrangler.jsonc, along with your own account_id and route, then:

npm run db:migrate:remote
npx wrangler secret put CONTACT_EMAIL
npm run deploy

CONTACT_EMAIL must be an address you actually read: the collector refuses to send a single request without one, because an unreachable contact in a User-Agent is worse than none.

/health reports catalogue freshness, guard state and any parser warnings.

How it works

Cloudflare Workers, D1 for the index, one Durable Object for MCP sessions. A cron trigger fires every minute and performs exactly one unit of work: refresh a batch of availability, advance one page of one crawl, or enrich one event page. The cron cadence is the rate limit, and each tick gets a fresh CPU budget. docs/ARCHITECTURE.md has the details.

Licence

Code is MIT, see LICENSE. The data is not: it belongs to the Cité de la musique – Philharmonie de Paris and is neither redistributed nor relicensed here. See NOTICE.