SeatGeek MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on when using HTTP transport | 8080 |
| MCP_HTTP | No | Set to any value to enable HTTP transport instead of STDIO | |
| SEATGEEK_SECRET | No | Your SeatGeek API secret | |
| SEATGEEK_CLIENT_ID | Yes | Your SeatGeek API client ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_eventsA | Search for events by performer, location, date, or venue. This tool is optimized for finding specific events based on user queries. If the query involves a performer, it first looks up the performer, then finds events for that performer. Otherwise, it searches events directly. Returns structured event data with venue information. |
| find_event_recommendationsB | Get personalized event recommendations based on performers, events, or location. This tool first searches for performers and/or events based on the query (q parameter), then uses the IDs to find similar events. Use location parameters (geoip, lat/lon, postal_code) for nearby events. |
| find_performer_recommendationsB | Get personalized performer recommendations based on performers, events, or location. This tool first searches for performers and/or events based on the queries, then uses the IDs to find similar performers. Use location parameters (geoip, lat/lon, postal_code) for nearby performers. |
| retrieve_event_venue_informationB | Get detailed seating information including sections and rows for a specific event. This tool first searches for the event using the provided query, then retrieves detailed venue layout information. Useful for understanding venue seating options and making ticket purchasing decisions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have distinct primary purposes: find_event_recommendations and find_performer_recommendations focus on personalized recommendations, find_events is for direct event searches, and retrieve_event_venue_information handles seating details. However, find_event_recommendations and find_events both involve event searches, which could cause some confusion if an agent needs to decide between them for a simple event lookup.
All tool names follow a consistent verb_noun pattern with clear, descriptive terms: find_event_recommendations, find_events, find_performer_recommendations, and retrieve_event_venue_information. The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for an event and performer discovery server, covering core functionalities like searching, recommendations, and venue details. It is slightly lean but well-scoped, as each tool serves a distinct role without unnecessary duplication.
The tool set covers key aspects of event discovery, recommendations, and venue information, but there are notable gaps. For example, it lacks tools for ticket purchasing, event creation/updates, or user-specific actions like saving favorites, which might be expected in a full SeatGeek integration. This could limit agent workflows in more complex scenarios.