FrontRowTickets.com MCP Server

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

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
95%
이름 품질
100%
오염 위험
100%
권한 일치
100%
프로토콜 준수
100%

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~1,019토큰 (도구 정의)
~1.4 KB일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 0.80%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

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

원격 엔드포인트

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

할 수 있는 일

도구 목록

도구 (4)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢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.

입력 스키마

{
  "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.

입력 스키마

{
  "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.

입력 스키마

{
  "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.

입력 스키마

{
  "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#"
}

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 4개