mcpbeat Sign in

Events MCP Server

by urbanplayground Your server? Claim it
answering

Events is answering right now. Last checked 14 min ago. 42 installs a week from npm. It exposes 31 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 9 · avg 5 · +38% w/w
a month agotoday
Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
31
Tools
read from the server
350 ms
Response time
average over 24h
42
Installs / week
npm and PyPI

What changed 183

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

21 Oct a tool appeared get_dizko_onboarding
14 Oct 27 tools changed the parameters they ask for add_to_dizko_plan, bin_event, create_event_calendar_file and 24 more
14 Oct 19 tool descriptions were rewritten22 times that day create_event_calendar_file, create_event_preference_profile, delete_event_preferences and 16 more
14 Oct a tool changed version
20 Sep 2 tool descriptions were rewritten bin_event, get_taste_profile
20 Sep 2 tools appeared bin_event, get_taste_profile
19 Sep 4 tools appeared add_to_dizko_plan, get_artist, get_venue and 1 more
19 Sep 3 tools changed the parameters they ask for plan_night, recommend_events, search_events
19 Sep a tool changed version
2 Sep a tool changed version2 times that day
and 122 more, back to 24 August 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add events --transport http https://eventchat-events-mcp-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "events": {
      "type": "http",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

Available tools 31

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 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.
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 links.
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.
artist
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 profile's saved featuring list.
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.
dizko
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.
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 pricing/signup/billing links. Read-only: never claims, publishes or charges. Use once at setup or when the user asks about their own page; do not interrupt event searches.
recommend
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.
save
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.
ticket
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 hand_off_to_checkout.
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.
bin
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.
cities
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.
city
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 inventory only.
daily
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 rank the picks. Pass compact=true for a short push-style digest.
events
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 saved taste (saved taste ranks results, it never filters them). Filters you pass (genres, vibe, event_types, price_max, venue, featuring) are hard filters; `avoid` and `max_price` are ranking hints. When nothing matches, the result carries `no_results` with how many events exist without the filters and ordered `suggested_relaxations` you can retry directly.
plan
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. An empty plan carries the same `no_results` guidance as search.
preference
get_preference_onboarding
Use this when a user wants consent-first questions before saving event preferences.
purchase
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_checkout and the checkout_url where the user pays on the provider's site. Never claim a purchase unless status is purchased. Each quote_token can be submitted once: a repeat returns status quote_already_used and must never be retried.
quote
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 confirmation text to ask the user for. Without an integrated provider it only prepares a hand off to checkout.
record
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 the notes blame the music.
scene
find_scene_entities
Use this when a user asks who a DJ is or about a venue, collective, or promoter.
taste
get_taste_profile
Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events.
venue
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.

Endpoints

URLTransportStateLatencyChecked
https://eventchat-events-mcp-production.up.railway.app/mcp streamable-http answering 364 ms 14 min ago

Alternatives to Events

same job, measured the same way
Wullup Events
by wullup

Find concerts, parties, club nights, festivals and more across Germany.

1 tools answering
Gigora
by sezgimeydanci

Live-concert discovery: 44,000+ upcoming concerts worldwide by city, artist, genre or festival.

4 tools answering
Latino Events (events.lat)
by events

Find upcoming concerts, festivals and cultural events across Latin America.

answering
Onthecheap MCP
by chrischall

On the Cheap MCP — free and cheap events, deals and local guides across 14 US cities

208 installs/wk local only
Events MCP
by himanshusaleria

Discover tech events, startup meetups, AI events across 8 cities — including hidden ones.

46 installs/wk 3 tools answering
Nhimbe Events
by mukoko

Discover and manage community events across Africa on Nhimbe (Mukoko Events).

answering
MCP Launcher
by oneprofile-dev

Single MCP hub: discover, add, audit, and govern MCP servers across every AI client.

61 installs/wk local only
SyncSo
by syncso

Live New York events, shows, classes, tours, markets, music, theater, comedy, art and nightlife

answering

Events — questions

Answers built from our own checks of this server.

What can Events do?
It exposes 31 tools, read directly from the server on our last check. Among them: add_to_dizko_plan, bin_event, create_event_calendar_file, create_event_preference_profile, delete_event_preferences, find_scene_entities and 25 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, artist and dizko. 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 91 of 91 checks got a reply (100.0%), average response time 350 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 in the form 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 31 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 350 ms on average, which is faster than 40% 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 42 times in the last week. Week over week that is +38%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.