Events MCP Server

xyz.urbanplayground/events

answering

Events is answering right now. Last checked 1 min ago. 22 installs a week from npm. It exposes 21 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 24 · avg 7 · -27% w/w

a month agotoday

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

356 ms

Response time

average over 24h

Installs / week

npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "events": {
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.events]
url = "https://eventchat-events-mcp-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "events": {
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "events": {
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

event

create_event_calendar_file

Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets.

create_event_preference_profile

Use this when a user explicitly agrees to save event preferences and does not already have a Dizko preference profile.

delete_event_preferences

Use this only when a user asks to delete their Dizko saved event preferences and feedback history.

get_event

Use this when a user asks for details about a specific Dizko event id returned by search, recommendations, or a night plan.

get_event_feedback_prompt

Use this when a user previously picked or attended a Dizko event and the assistant should ask a short post-event follow-up before recording feedback.

get_event_preferences

Use this when a user with a Dizko profile wants to view saved event preferences or learned recommendation signals.

get_event_search_followups

Use this when a user asks for events tonight, this week, or this weekend and the assistant should ask only the missing event type, vibe, budget, area, or avoid-preference questions before searching.

recommend

recommend_events

Use this when a user wants ranked event suggestions from live Dizko inventory based on the current request's taste, vibe, price, and avoid signals.

recommend_events_for_user

Use this when a user has a Dizko preference profile and wants personalized event recommendations for tonight, this week, this weekend, or another date range.

ticket

get_ticket_offers

Use this when a user wants ticket options for a specific Dizko event before quoting or buying.

get_ticket_purchase_policy

Use this when a user asks whether agents can buy tickets autonomously or what purchase modes Dizko, Hermes, OpenClaw, or other providers can support.

artist

get_artist_events

Use this when a user asks when specific DJs, performers, or comedians play next, or wants upcoming shows for the artists they follow. Pass artists explicitly, or pass only profile_id and profile_secret to use the artists saved in the profile's featuring list.

city

get_city_pulse

Use this when a user asks what is hot, where the momentum is, or how busy a city's event scene looks over the coming days. Returns busiest nights, top venues, genre mix, and headline events from aggregate public inventory, every stat with evidence counts.

daily

get_daily_roundup

Use this when a user wants a daily digest of what is happening in a city today, tomorrow, or on a specific date: top picks plus parties, live music, art, comedy, talks, and food sections from live Dizko inventory. Ideal for recurring morning briefings; pass profile_id and profile_secret so saved, learned, and per-day (day_filters) preferences shape the picks.

events

search_events

Use this when a user wants current events from live Dizko inventory using filters such as city, date, genre, vibe, venue, artist, neighborhood, or price.

plan

plan_night

Use this when a user wants a compact night-out plan with a primary live event option and fallback options from Dizko inventory.

preference

get_preference_onboarding

Use this when a user wants personalized event recommendations and Dizko needs consent-first questions before saving event preferences.

purchase

purchase_ticket_order

Use this when the user has given explicit written confirmation for a locked ticket quote and the agent should either execute an integrated provider purchase or return the required external checkout handoff.

quote

quote_ticket_order

Use this when a user has chosen an event and wants a locked ticket quote with quantity, max price, ticket type, and stop conditions before any purchase attempt.

record

record_event_feedback

Use this when a user says whether they liked or disliked a specific event, provides a rating, or shares notes, so future Dizko recommendations can learn from that feedback.

save

save_event_preferences

Use this when a consenting user already has a Dizko profile and wants to add, update, merge, or replace saved event preferences.

Endpoints

URL	Transport	State	Latency	Checked
https://eventchat-events-mcp-production.up.railway.app/mcp	streamable-http	answering	338 ms	1 min ago

Events — questions

Answers built from our own checks of this server.

What can Events do?

It exposes 21 tools, read directly from the server on our last check. Among them: create_event_calendar_file, create_event_preference_profile, delete_event_preferences, get_artist_events, get_city_pulse, get_daily_roundup and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Events mostly used for?

Its tools cluster around event, recommend and ticket. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Events working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 356 ms. The bar chart above shows every period we have measured.

Is Events still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Events?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Events need an API key?

No. Events completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Events?

It answers our handshake in 356 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Events?

The npm package uplayground-events was installed 22 times in the last week. Week over week that is -27%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.