
Ticket Discovery
io.github.wmarceauPublished by GitHub account wmarceauv1.0.0Updated Oct 28, 2026
Search and compare concert ticket prices across platforms
Overview
Local MCP server that lets an assistant search and compare concert ticket prices across ticketing platforms such as SeatGeek and Ticketmaster.
- What you can do
- Search concert and event ticket listings across ticketing platforms
- Compare prices for the same event between platforms
- Work with SeatGeek data, optionally including affiliate commission tracking
- Work with Ticketmaster Discovery event data
- When to use it
- Useful when you want an assistant to look up concerts or events and compare ticket prices across platforms before buying. It fits personal event planning and price checking rather than purchasing or booking.
- Requirements
- Runs as a local process installed from the PyPI package ticket-discovery-mcp over stdio, so a Python environment is needed. Requires a SeatGeek API client ID (SEATGEEK_CLIENT_ID) and a Ticketmaster Discovery API key (TICKETMASTER_API_KEY), both free to obtain. Optional: SEATGEEK_CLIENT_SECRET and SEATGEEK_AFFILIATE_ID. Network access to the ticketing APIs is required.
Installation
In SourceWeft
- Open Ticket Discovery in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.