bots.st/urbanplayground-xyz
events
Find concerts and events by city
1624 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 31
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://eventchat-events-mcp-production.up.railway.app/mcp - npm
npx -y uplayground-eventsReleased 11 Jun 2026, version 0.3.0
What it can do
| Tool | What it says it does |
|---|---|
add_to_dizko_plan | Use this when a user confirms they want to add one Dizko event to the connected user's persistent plan only after explicit confirmation. |
bin_event | Use this only when the user confirms an event is not for them. It hides the event and teaches their Dizko taste model. |
create_event_calendar_file | Use this when the user wants one event in Apple Calendar, Google Calendar or Outlook as a file. Builds an importable .ics entry (local time, venue address, lineup, set times, links); the per-event calendar_url is the one-click alternative. |
create_event_preference_profile | Use this only when the user has explicitly agreed to let Dizko save their taste. Creates a private preference profile and returns profile_id and a one-time profile_secret to keep for future personalized calls. Ask the onboarding questions (get_preference_onboarding) first; consent must be true. |
delete_event_preferences | Use this only when the user confirms they want their Dizko connector data deleted. Deletes a profile's saved preferences and feedback history; confirm_delete must be true. Scoped to Dizko only. |
find_scene_entities | Use this when a user asks who a DJ is or about a venue, collective, or promoter. |
get_artist | Use this when a user wants a canonical artist profile, graph context, published links, and upcoming events. Pass an id or a name query; this does not enumerate the artist catalog. |
get_artist_events | Use this when a user asks when a DJ, performer or comedian plays next, or whether they play in a city this month. Returns upcoming shows grouped by artist for up to 8 names, deduplicated across sources and date-ordered, optionally scoped to a city. With a profile and no artists named, tracks the… |
get_artist_page | Use this when a user wants an artist's Dizko page or a specific published mix or set. Returns the page embeds with stable block ids for deep links. |
get_city_pulse | Use this when a user asks what's hot, how busy a city is this week, or about scene trends. Returns an aggregate read over the coming days: busiest nights (city-local dates), top venues (attendance-weighted), genre mix, headline events and free-event count, every stat with evidence counts. Public… |
get_daily_roundup | Use this when a user asks what's happening today or tomorrow, or for a morning briefing or scheduled check-in. Returns a one-day digest for a city: top picks plus sections for parties, live music, art, comedy and theatre, talks, food, and more. With a profile, saved, learned and per-weekday taste… |
get_dizko_onboarding | Use this when someone wants optional Dizko setup for event discovery or for DJs, artists, musicians, venues, collectives and promoters. With SoundCloud, checks exact database matches and returns claim/create guidance, real published page examples, site-builder benefits and website… |
get_event | Use this only when the user gives an event id, or wants extra detail on an event not in the current results; search results already contain what the template needs. Returns full detail for one event: local times, venue and address, price, lineup, set times, artist socials, image, coordinates and… |
get_event_feedback_prompt | Use this when a user needs a short post-event feedback prompt. |
get_event_preferences | Use this when the user asks what Dizko remembers about them. Returns a profile's saved preferences, learned taste (with scores) and feedback count. |
get_event_search_followups | Use this when an event search needs follow-up questions. |
get_preference_onboarding | Use this when a user wants consent-first questions before saving event preferences. |
get_taste_profile | Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events. |
get_ticket_offers | Use this when the user wants tickets for one event, before quoting. Returns ticket options: provider, checkout link, estimated price, whether entry is free, whether autonomous purchase is supported, next_step, and the purchase policy. On the hosted connector Dizko does not buy tickets: next_step… |
get_ticket_purchase_policy | Use this when a user asks how Dizko agents can buy tickets: signed quote, written confirmation, then a hand off to checkout unless a provider is integrated. |
get_venue | Use this when a user wants a canonical venue profile, graph context, and upcoming events. Pass an id or a name query; this does not enumerate the venue catalog. |
list_cities | Use this when a user asks where Dizko works, whether a city is covered, or how fresh the data is. Returns every city with status (live, unlocking, early), event count, timezone and freshness. Unlocking and early cities are searchable but thin. |
plan_night | Use this when the user wants a night plan with backups rather than a list. Returns, for one city and date, a primary event plus a nearby fallback (best taste fit within 6 km), a later-starting fallback, and alternates. Accepts the same filters as search_events and an optional profile for saved… |
purchase_ticket_order | Use this only when the user has confirmed a quote in writing (the confirmation must say buy or purchase and repeat the quantity and max total; the server rejects it otherwise). Without an integrated purchase provider this buys nothing: it hands off to checkout, returning status… |
quote_ticket_order | Use this when the user has chosen a ticket offer, quantity and constraints. Creates a signed, time-limited quote (quantity, ticket type, max total, currency, refund terms, delivery email, stop conditions) and returns a quote_token to pass unchanged to purchase_ticket_order plus the exact… |
recommend_events | Use this when a user wants live events ranked by taste, vibe, price, and exclusions. Every result carries recommendation_reasons. Request filters (genres, vibe, event_types, price_max, venue, featuring) are hard filters; avoid and max_price only rank. |
recommend_events_for_user | Use this when a user wants recommendations personalized with a saved Dizko profile. Saved and learned taste rank the results; they never hide them. |
record_event_feedback | Use this only when the user has answered post-event questions (get_event_feedback_prompt has them). Stores liked, a 1-5 rating or notes for a profile and updates learned taste: a like promotes the event's genres, vibe and venue; a dislike marks the venue and promoter, and only penalizes genres… |
save_event | Use this when a user confirms they want to save one Dizko event to the connected user's account only after explicit confirmation. |
save_event_preferences | Use this when the user shares new taste for an existing profile: genres, favorite artists to track (featuring), venues, budget, or per-weekday rules (day_filters). Adds to (mode merge) or replaces saved preferences. Needs profile_id, profile_secret and consent=true. |
search_events | Use this when a user asks what's on and names a city, a venue, an artist, or a timeframe. Returns up to `limit` live events with local times (`when`), venue and address, price, genres, vibe, lineup, set times and links; `count` is the total matching. Pass profile_id and profile_secret to rank by… |
In its maker's words
Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.
- Website
- urbanplayground.xyz
- Source
- github.com/ZakKrevitt/EventChat
- Publisher
- urbanplayground.xyz
- Listed from
- the official MCP Registry as
xyz.urbanplayground/events - Version
- 0.3.0, updated 11 Jun 2026
- Kinds of work
- Travel, maps and weather, Search and research, Messaging and support
The domain it lives on
- urbanplayground.xyz
- registered 15 May 2026 (6 months ago), at Name.com, Inc
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1624 ms | |
| Answered | 1576 ms | |
| Answered | 437 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.