FrontRowTickets.com MCP Server

Live FrontRowTickets.com ticket inventory for AI agents: search, availability, pricing, deals.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
95%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,019Tokens (definiciones de herramientas)
~1.4 KBTamaño de respuesta típico
Impacto moderado en la atención (0.80% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "frontrowtickets-mcp": {
      "url": "https://mcp.frontrowtickets.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://mcp.frontrowtickets.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (4)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢search_events(query, city, date_from, date_to, category, ...)

Start here for discovery: search FrontRowTickets.com ticket inventory by free text, city, date range, and category (sports, concerts, theater, comedy). All filters are optional and combine freely; returns up to 'limit' events (default 10, max 50, no further pages), soonest first, with ticket counts and starting prices. Use get_event for one event's full record, get_deals when the user has a hard budget cap.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free text: team, artist, show, or venue name"
    },
    "city": {
      "type": "string",
      "description": "City name, e.g. Chicago"
    },
    "date_from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}",
      "description": "Earliest event date (ISO)"
    },
    "date_to": {
      "$ref": "#/properties/date_from",
      "description": "Latest event date (ISO)"
    },
    "category": {
      "type": "string",
      "enum": [
        "sports",
        "concerts",
        "theater",
        "comedy"
      ],
      "description": "One of sports, concerts, theater, comedy"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10,
      "description": "Max results returned (default 10, max 50)"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_event(event_id)

Full details for one event: venue, date, ticket count, price range, and sections. The record is live-refreshed from the catalog when called (cached copy otherwise), so this is the fullest picture of the event. Prefer get_availability when the only question is 'can I get N tickets at or under $X' — it answers that directly without the full record.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "event_id": {
      "type": "string",
      "description": "Event ID from search_events"
    }
  },
  "required": [
    "event_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_availability(event_id, max_price, quantity)

Answers 'can I get tickets for this event?' for one event: refreshed from the live source at call time, returning current availability and starting price. max_price is a hard gate — the event is reported only if its starting price is at or below it (otherwise availability:null with a note); quantity is informational context only, not a reservation. Use get_event when you need the event's full record, get_deals to browse by budget instead. Note: the catalog API does not expose section-level price bands, so only totals and the starting price are returned.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "event_id": {
      "type": "string",
      "description": "Event ID from search_events"
    },
    "max_price": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Hard gate in USD: the event is reported only if its starting price is at or below this"
    },
    "quantity": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "description": "Desired ticket quantity (informational context only; does not reserve)"
    }
  },
  "required": [
    "event_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_deals(city, max_price, date_from, date_to)

Use when budget is the primary filter: returns the cheapest available events under a required max_price cap (applied to each event's starting price), cheapest first, up to 25 results; events without pricing data are excluded. City and date range are optional additional filters. Use search_events for text- or category-driven discovery instead.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. Chicago"
    },
    "max_price": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Required. Maximum starting price in USD — events above this are excluded"
    },
    "date_from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}",
      "description": "Earliest event date (ISO)"
    },
    "date_to": {
      "$ref": "#/properties/date_from",
      "description": "Latest event date (ISO)"
    }
  },
  "required": [
    "max_price"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada4 herramientas