# Urbanplayground Events MCP server

Source: https://glimind.com/server/mcp-registry%2Fxyz.urbanplayground%2Fevents
Registry id: `mcp-registry/xyz.urbanplayground/events`
Status: live (checked 2026-10-26T23:24:46.213Z)

## Measurements (30 days)

- Uptime: 99.97%
- Checks: 4930
- Outages (90 days): 5

## Install

```json
{
  "mcpServers": {
    "urbanplayground-events-mcp-server": {
      "type": "http",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http urbanplayground-events-mcp-server https://eventchat-events-mcp-production.up.railway.app/mcp
```

## Tools (31)

- `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, line
- `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 prof
- `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 mu
- `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 
- `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 u
- `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-
- `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 pl
- `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 
- `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 ne
- `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, whe
- `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
- `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 fi
- `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 reject
- `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, re
- `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,
- `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 update
- `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_filter
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.