Un servidor de protocolo de contexto de modelo que proporciona herramientas para descubrir eventos, lugares y atracciones a través de la API de descubrimiento de Ticketmaster.
Busque eventos, lugares y atracciones con filtros flexibles:
Búsqueda de palabras clave
Rango de fechas para eventos
Ubicación (ciudad, estado, país)
Búsquedas específicas del lugar
Búsquedas específicas de atracciones
Clasificaciones/categorías de eventos
Formatos de salida:
Datos JSON estructurados para uso programático
Texto legible para consumo directo
Datos completos que incluyen:
Nombres e identificaciones
Fechas y horarios (para eventos)
Rangos de precios (para eventos)
URL
Imágenes
Ubicaciones y direcciones (para lugares)
Clasificaciones (para atracciones)
Related MCP server: Ticketmaster Partner API
npx -y install @delorenj/mcp-server-ticketmasterEl servidor requiere una clave API de Ticketmaster. Puedes obtenerla de la siguiente manera:
Crear una cuenta o iniciar sesión
Vaya a "Mis aplicaciones" en su cuenta
Creando una nueva aplicación para obtener tu clave API
Establezca su clave API en su archivo de configuración MCP:
{
"mcpServers": {
"ticketmaster": {
"command": "npx",
"args": ["-y", "@delorenj/mcp-server-ticketmaster"],
"env": {
"TICKETMASTER_API_KEY": "your-api-key-here"
}
}
}
}El servidor proporciona una herramienta llamada search_ticketmaster que acepta:
type : Tipo de búsqueda ('evento', 'lugar' o 'atracción')
keyword : término de búsqueda
startDate : Fecha de inicio en formato AAAA-MM-DD (para eventos)
endDate : Fecha de finalización en formato AAAA-MM-DD (para eventos)
city : Nombre de la ciudad
stateCode : código de estado (p. ej., 'NY')
countryCode : Código de país (por ejemplo, 'EE. UU.')
venueId : ID de lugar específico
attractionId : ID de atracción específica
classificationName : Categoría del evento (p. ej., 'Deportes', 'Música')
format : Formato de salida ('json' o 'texto', predeterminado 'json')
<use_mcp_tool>
<server_name>ticketmaster</server_name>
<tool_name>search_ticketmaster</tool_name>
<arguments>
{
"type": "event",
"keyword": "concert",
"startDate": "2025-02-01",
"endDate": "2025-02-28",
"city": "New York",
"stateCode": "NY"
}
</arguments>
</use_mcp_tool><use_mcp_tool>
<server_name>ticketmaster</server_name>
<tool_name>search_ticketmaster</tool_name>
<arguments>
{
"type": "event",
"keyword": "concert",
"startDate": "2025-02-01",
"endDate": "2025-02-28",
"city": "New York",
"stateCode": "NY",
"format": "text"
}
</arguments>
</use_mcp_tool>Clonar el repositorio
Copie el archivo de entorno de ejemplo:
cp .env.example .envAgregue su clave API de Ticketmaster a .env
Instalar dependencias:
npm installConstruir el proyecto:
npm run buildPrueba con el inspector:
npm run inspector¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios. Para cambios importantes, primero abra una incidencia para comentar qué desea cambiar.
Licencia MIT: consulte el archivo de LICENCIA para obtener más detalles
Search for events, venues, or attractions on Ticketmaster
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Type of search to perform | |
| keyword | No | Search keyword or term | |
| startDate | No | Start date in YYYY-MM-DD format | |
| endDate | No | End date in YYYY-MM-DD format | |
| city | No | City name | |
| stateCode | No | State code (e.g., NY, CA) | |
| countryCode | No | Country code (e.g., US, CA) | |
| venueId | No | Specific venue ID to search | |
| attractionId | No | Specific attraction ID to search | |
| classificationName | No | Event classification/category (e.g., "Sports", "Music") | |
| format | No | Output format (defaults to json) | json |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions searching but doesn't disclose rate limits, authentication needs, pagination, error handling, or what happens with partial/no results. This is inadequate for a search tool with 11 parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It earns its place by clearly stating the tool's function in minimal space.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex search tool with 11 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavior, output format (beyond the 'format' parameter), error cases, and usage context, leaving significant gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond implying search across multiple resource types, which aligns with the 'type' parameter. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Search') and resources ('events, venues, or attractions on Ticketmaster'), making the purpose immediately understandable. It doesn't need to distinguish from siblings since none exist, but it could be more specific about what 'search' entails (e.g., listing vs. filtering).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives or any prerequisites. The description merely states what it does without context about appropriate scenarios, limitations, or integration with other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.2.5search_ticketmasterScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching for events, venues, or attractions, making it straightforward for an agent to understand its function without confusion.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_ticketmaster' follows a clear verb_noun pattern, which would be consistent if more tools were added, but as a standalone, it sets a good precedent.
A single tool is too few for a server focused on Ticketmaster events, which typically involves operations like browsing events, getting details, checking availability, or purchasing tickets. This minimal set feels thin and incomplete for the apparent scope, limiting agent capabilities.
The tool surface is severely incomplete for the domain of Ticketmaster events. While search is a useful starting point, there are obvious gaps such as retrieving event details, listing venues, checking ticket availability, or handling bookings, which are essential for comprehensive event management workflows.
Ticketmaster Discovery v2 MCP.
Google Events listings with dates, venues, and ticket links via a hosted MCP server.
Live event ticket market data: prices, inventory, demand and seat maps, with screens and alerts.
European and US event data from Eventbrite: dates, venues, categories, ticket prices, organizers.