INDIVIDUAL MCP TOOL

get_event_preferences

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

urbanplayground.xyznone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for get_event_preferences and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

urbanplayground.xyz

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.

Related tools

get_preference_onboarding — Use this when a user wants personalized event recommendations and Dizko needs consent-first questions before saving event preferences.
create_event_preference_profile — Use this when a user explicitly agrees to save event preferences and does not already have a Dizko preference profile.
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.
delete_event_preferences — Use this only when a user asks to delete their Dizko saved event preferences and feedback history.
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.
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_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.
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.