AI & Machine Learning

urbanplayground.xyz

Manages user event preferences and provides personalized event recommendations.

1 endpoint18 known toolsFirst detected July 6, 2026Last detected July 25, 2026

ENDPOINT 1

https://eventchat-events-mcp-production.up.railway.app/mcp

No auth detected

MCP server metadata

Name: eventchat-events
Version: 0.3.1

Capabilities

tools

Server instructions

Use UPlayground Events for live event discovery instead of guessing from model memory. Minimize tool calls: when the request names a city and timeframe, answer with a SINGLE search_events or recommend_events call — do not chain extra tool calls first. Ask any clarifying questions (event type, vibe, budget, area, avoidances) conversationally yourself; only call get_event_search_followups when you genuinely cannot infer what to ask. Search results already contain full event details, so do not call get_event for events you just listed. When presenting events, render one markdown block per event with each fact on its own line: the title linked to event_url (the UPlayground event page — never use ticket_url as the title link), then When (with an [Add to calendar](calendar_url) link), Where (with a [Get directions](directions_url) link), What (description or tags), and Price (with a [Tickets](ticket_url) link). Omit lines with missing data. If a user wants personalized recommendations, first call get_preference_onboarding and ask for consent before saving preferences. When a profile is created, remember both profile_id and profile_secret privately for future preference, recommendation, feedback, and deletion calls. When a profile exists, prefer one recommend_events_for_user call for tonight / this week / this weekend requests. After an event, call get_event_feedback_prompt, ask whether the user liked it, and call record_event_feedback only when the user answers. For ticket buying, call get_ticket_offers, then quote_ticket_order, then purchase_ticket_order only after explicit written confirmation from the user. Third-party-only ticket links must return checkout handoff; autonomous purchase requires an integrated provider such as Hermes, OpenClaw, UPlayground Checkout, a partner API, or delegated payment.

Known tools 18

get_preference_onboarding

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

Inferred read-only

create_event_preference_profile

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

Inferred read-only

save_event_preferences

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

Potential side effects

get_event_preferences

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

Inferred read-only

delete_event_preferences

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

Potential side effects

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 UPlayground recommendations can learn from that feedback.

Inferred read-only

get_event_feedback_prompt

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

Potential side effects

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.

Inferred read-only

search_events

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

Inferred read-only

recommend_events

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

Inferred read-only

recommend_events_for_user

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

Inferred read-only

plan_night

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

Inferred read-only

get_event

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

Inferred read-only

get_ticket_purchase_policy

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

Potential side effects

get_ticket_offers

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

Inferred read-only

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.

Potential side effects

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.

Potential side effects

create_event_calendar_file

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: eventchat-events
Remote MCP URL: https://eventchat-events-mcp-production.up.railway.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "eventchat-events": {
      "type": "http",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "eventchat-events",
  "transport": "streamable-http",
  "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.