Connect-MCP

xyz.urbanplayground/events

xyz.urbanplayground/events · v0.3.0

Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.

MCPremotelocal · npmno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 30 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 94/100

What it does: 30 tools · 22 read, 8 write (incl. delete/pay)

Test call list_cities: worked (1,108 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +4
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://eventchat-events-mcp-production.up.railway.app/mcp
Package
registry:   npm
identifier: uplayground-events
version:    0.3.0
transport:  stdio

Tools

30 tools listed at last check
  • get_preference_onboarding Use this when a user wants consent-first questions before saving event preferences.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 when
  • get_event_feedback_prompt Use this when a user needs a short post-event feedback prompt.
  • get_event_search_followups Use this when an event search needs follow-up questions.
  • 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.
  • 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_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.
  • 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 sav
  • 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.
  • 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 taste
  • 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 ra
  • 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 pro
  • 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 inv
  • 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 lin
  • 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_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 is
  • 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 confirmatio
  • 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 requires_external_che
  • get_taste_profile Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events.
  • 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.
  • 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.
  • 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.
  • 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.

Badge

Connect-MCP badge for xyz.urbanplayground/events

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/xyz.urbanplayground/events.svg)](https://clawy.uk/mcp/s/xyz.urbanplayground/events)

Repository · Website