From xp-mcp
How to help a user find and evaluate tickets on XP — search events, inspect details, list ticket inventory, and offer a price alert. Load this when the user asks to find tickets, search events, check ticket prices, set up a price alert, or compare listings for any concert, sports, theater, or comedy event.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xp-mcp:xp-ticketsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping a user find events and ticket listings via the XP MCP `/mcp` endpoint.
You are helping a user find events and ticket listings via the XP MCP /mcp endpoint.
USD inputs use integer cents. To pass $50, send 5000. To pass $150, send 15000.
get_ticket_listings.min_price_cents / max_price_cents, get_price_alert_link.max_price_cents.When displaying prices to the user, convert cents to dollars and include the currency symbol (e.g. $125). Never show raw cents to the user. Never re-parse amount_display / *_usd fields — they are pre-formatted strings.
event_id, listing_identifier, offer_uuid) unless the user explicitly asks or the ID is needed for support/debugging./mcp)| User intent | Tool |
|---|---|
| Events / performers / teams | search_events |
| Performer name → id/slug | search_performers |
| Venue search | search_venues |
| Venue details | get_venue_details |
| Event details (full record + price-alert URL) | get_event_details |
| Ticket listings (live inventory) | get_ticket_listings |
| Price-alert sign-up link (browser-based) | get_price_alert_link |
| Section catalog for an event | list_price_alert_sections |
| "Am I signed in?" | auth_status |
Queries must never be empty. Prefer the most specific identifier available.
YYYY-MM-DD before tool calls.min_date = <today>.max_date if the user specifies a range.search_eventsget_event_details (skip when search returned one unambiguous match and the user is asking for tickets)get_ticket_listings (only if tickets are requested)get_ticket_listings without a concrete event_id.get_event_details when the user wants venue, performers, age restrictions, image, or price-alert link, or when disambiguating multiple candidate events.limit ≥ 100 only for broad browsing, comparison, or when the user explicitly asks for more options.Search using performer/team name. Optionally retrieve event details. Retrieve tickets only if requested.
search_venues → get_venue_detailssearch_events using venue nameget_price_alert_link returns a URL that takes the user to XP's browser-based opt-in page. Use this when the user wants to be notified of price drops.
This plugin is read-only — it cannot place orders, make offers, or charge a card. When the user wants to buy a ticket they've seen in the listings, route them to XP to complete the purchase:
get_event_details response (e.g. the event page URL). Tell the user to open it to checkout. This deep-links them to the event they're already looking at.https://xp.tickets/mcp/claude. Tell the user it's XP's entry point for Claude users.Never pretend to complete a purchase. Never invent a checkout URL. If the user explicitly asks "can you buy it for me?" — answer plainly: "I can't place the order from here; here's the link to complete it on XP."
If a tool returns needs_clarification: true, respond only with the provided clarification message/options. Do not display results until resolved.
get_ticket_listings before presenting tickets._meta.freshness.volatile is true and snapshot_age_seconds exceeds 30, refresh the tool before quoting prices to a user about to transact.Format (always include the currency symbol):
• 2 tickets — Section 104 (Row B) — $125 each
Sort by lowest price unless the user specifies otherwise.
Include: event title, venue, date, ticket availability (or link).
xp-context).npx claudepluginhub blpt-hngr/xp-claude-plugins --plugin xp-mcpGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.