Nightlife MCP

What alcylu/nightlife-mcp MCP server does

The alcylu/nightlife-mcp MCP server gives an MCP client access to nightlife data and request workflows. Its public-facing tools cover event discovery, venue lookup, performer information, and time-based searches such as tonight or a weekend. Results can include upcoming event snapshots for venues and performers.

The server also supports a concierge workflow for unresolved requests. Clients can record an unmet user intent in Supabase when the available nightlife data cannot answer it. For venues that have VIP booking enabled, clients can submit booking requests, check their status, inspect table availability, and retrieve a structured table chart.

How it works

The service uses Supabase for nightlife records, API-key data, booking requests, queue tasks, and VIP inventory. City handling is based on city records containing a slug, timezone, and service-day cutoff. Tokyo is the default city, but the top-level city list can be configured through the environment.

MCP is available through a Streamable HTTP endpoint at https://api.nightlife.dev/mcp. HTTP authentication is enabled by default and accepts either an x-api-key header or a Bearer token. The local stdio transport does not perform an API-key check. HTTP deployments can use persistent keys stored in Supabase, with optional environment-key fallback and quota headers.

Setup and configuration

To run the alcylu/nightlife-mcp MCP server from the repository, use Node.js 18 or later, provide a Supabase project URL and service-role key, copy .env.example to .env, and run npm install. The repository documents npm run dev for local stdio operation, npm run dev:http for development HTTP mode, and npm run build followed by npm start for a production build.

Set SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY. Useful optional settings include DEFAULT_CITY, DEFAULT_COUNTRY_CODE, NIGHTLIFE_BASE_URL, and MCP_TOP_LEVEL_CITIES. HTTP authentication behavior is controlled by MCP_HTTP_REQUIRE_API_KEY, MCP_HTTP_USE_DB_KEYS, MCP_HTTP_ALLOW_ENV_KEY_FALLBACK, and MCP_HTTP_API_KEYS.

The hosted endpoint requires a free API key from nightlife.dev. For database-backed authentication, apply the documented Supabase migration and create a key record with the repository's key command. VIP workflows require their corresponding database migrations; recommendation tools require MCP_ENABLE_RECOMMENDATIONS=true.

Tools and capabilities

The alcylu/nightlife-mcp MCP server implements tools for:

• Searching events and retrieving tonight's events
• Getting event details
• Searching venues and performers, then retrieving individual records
• Recording unmet concierge requests
• Requesting VIP bookings and checking booking status
• Reading VIP table availability and table charts
• Generating recommendations when the feature flag is enabled

Internal operations also include reservation queue management, booking status updates, venue table maintenance, availability updates, and chart-image uploads. These operations are intended for internal booking workflows rather than ordinary discovery clients.

Limitations and notes

VIP submissions are accepted only for venues marked as supporting VIP booking. Clients should confirm the local booking date and time before submitting, particularly for arrivals between midnight and 5:59 AM. Date filters support tonight, this_weekend, single dates, and date ranges.

HTTP API-key requirements can be changed by configuration, while local stdio runs without that check. The recommendation tool is disabled by default. The server exposes /health for runtime request and tool metrics and provides deterministic JSON error payloads for documented invalid or missing event, venue, performer, and booking inputs.