Luma MCP server

@pipeworx/luma

Public event discovery from Luma (lu.ma): curated city feeds, one event's full detail, and an organizer's public calendar — the same data a browser sees on lu.ma/discover and on each event's own public page.

Part of Pipeworx — an MCP gateway connecting AI agents to 1800+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

placeid, coordinates, timezone and live eventcount. Use to find a placeid for lumaevents, or just pass a city name directly.

• luma_places(query?, limit?) — list Luma's curated discover cities, with

upcoming events for a discover city. Pass a city name (resolved for you against lumaplaces) or a placeid. An optional keyword filters on event name/venue/organizer, matched client-side.

• lumaevents(city? | placeid?, query?, limit?, cursor?) — list public

timing, venue, categories, ticket types, FAQs, hosts and calendar.

• lumaevent(eventid) — full public detail for one event: description,

events on an organizer's calendar page (a company's or community's event series).

• lumacalendarevents(calendar_id, limit?, cursor?) — public upcoming

None of these return guest lists or attendee data — see "Privacy" below.

Auth

Keyless. No account, API key or registration needed — these are Luma's own public discovery endpoints, the same ones a signed-out browser calls.

Data sources

event pages, and organizer calendar pages, all served to any visitor without an account.

• Luma, public event-discovery feed — city "discover" pages, individual

Privacy

Luma's own payload for an event carries per-event attendee signal: a guest count, and for well-attended events a "featured guests" list naming and showing avatars for people who RSVP'd, plus (for an authenticated caller) their own RSVP record. This pack strips all of it before returning anything — guestdata, featuredguests, guestinfo, hostinfo and manager_info are dropped in every tool. Only the event itself, its public organizer/host listing (the people or orgs who publicly listed themselves as running the event — a different thing from attendees), and its calendar are returned.

Notes

on the discover-events endpoint does not actually filter server-side (verified live: identical result sets with and without it for the same place), so this pack paginates the upstream itself (up to 200 events) and matches on event name, venue and organizer name instead.

• luma_events's query filters client-side. Luma's own query parameter

live discover-places list by exact name/slug first, then by substring. There is no local cache of places — each resolution is a fresh call, since the list is small (under 100 cities) and changes as Luma launches new ones.

• Place/city resolution (luma_events given a city) matches against the

The easiest way to get one is from a prior lumaevents or lumacalendarevents call — every returned event carries its own eventid, and its calendar.url leads to the organizer's public page.

• Event and calendar IDs (evt-..., cal-...) are opaque Luma identifiers.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "luma": {
      "url": "https://gateway.pipeworx.io/luma/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/luma/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.