F
licenseB
qualityD
maintenanceConnects Claude to the Ticketmaster API to let users discover local events by city, category, keyword, or weekend through natural conversation.
4
-
etix-mcp
by chrischall
Related Servers
Alternatives to etix-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceLive-concert discovery MCP server: search concerts, artist tour dates, festivals and shows by city. Gives AI assistants real-time access to Gigora's global live-music data.-
- FlicenseNot gradedqualityDmaintenanceAn MCP Server that enables interaction with Ticketmaster's Discovery API for accessing event, venue, and artist information through natural language commands.-
- AlicenseNot gradedqualityDmaintenanceMCP server for StubHub — search events, compare ticket prices, and purchase tickets via browser automation.8 npmMIT
- FlicenseBqualityDmaintenanceThis server integrates with the Ticketmaster API to provide AI agents with real-time concert and event data, enabling dynamic fetching and formatting for ease of interpretation.12-
- FlicenseAqualityBmaintenanceMCP server that wraps the AddEvent Calendar & Events API v2, allowing Claude to create, search, retrieve, update, and delete events, calendars, and RSVP attendees, plus list timezones.16-
TDQS
A4.4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: healthcheck diagnoses connectivity, find_location geocodes, search finds entities by keyword, get_event and get_venue fetch details by id. No overlap or ambiguity between tools.
Naming Consistency4/5
All tools share a consistent etix_ prefix and snake_case formatting, which is highly predictable. Minor deviations: etix_healthcheck is a noun rather than verb_noun, and etix_search lacks an object noun, but the pattern remains readable.
Tool Count5/5
Five tools is well-scoped for a read-only public event discovery API. Each tool earns its place: search, two detail fetchers, a geolocation helper, and a diagnostic tool.
Completeness3/5
Core read paths are covered (search -> get_event/get_venue), but find_location is a dead end because no tool accepts coordinates to find events, and there is no performer-detail endpoint. These notable gaps limit location-based browsing and deep entity traversal.
Maintenance
ActivityActive
ResponsivenessResponsive