Browse, search, and export public Luma events from one Go binary — no account, no API key, plus offline full-text search the public API doesn't have.
luma reads Luma's public discovery surface (api.luma.com) to list events by city and category, fetch full event and calendar details, and mirror it all into a local SQLite store. On top of the raw API it adds what Luma never exposed publicly: full-text search, geo-radius lookup, cross-city aggregation, change tracking, and ICS export — all agent-native with --json and --select.
Learn more at Luma.
Created by @richardadonnell (richardadonnell).
The recommended path installs both the luma-pp-cli binary and the pp-luma agent skill (Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, and other agents supported by the upstream skills CLI) in one shot:
npx -y @mvanhorn/printing-press-library install lumaFor CLI only (no skill):
npx -y @mvanhorn/printing-press-library install luma --cli-onlyFor skill only — installs the skill into the same agents as the default command above, but skips the CLI binary (use this to update or reinstall just the skill):
npx -y @mvanhorn/printing-press-library install luma --skill-onlyTo constrain the skill install to one or more specific agents (repeatable — agent names match the skills CLI):
npx -y @mvanhorn/printing-press-library install luma --agent claude-code
npx -y @mvanhorn/printing-press-library install luma --agent claude-code --agent codexIf npx isn't available (no Node, offline), install the CLI directly via Go (requires Go 1.26.4 or newer):
go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/luma/cmd/luma-pp-cli@latestThis installs the CLI only — no skill.
Download a pre-built binary for your platform from the latest release. On macOS, clear the Gatekeeper quarantine: xattr -d com.apple.quarantine <binary>. On Unix, mark it executable: chmod +x <binary>.
Install the CLI binary first. The installer writes binaries to a per-user managed bin directory by default: $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows.
npx -y @mvanhorn/printing-press-library install luma --cli-onlyThen install the focused Hermes skill.
From the Hermes CLI:
hermes skills install mvanhorn/printing-press-library/cli-skills/pp-luma --forceInside a Hermes chat session:
/skills install mvanhorn/printing-press-library/cli-skills/pp-luma --forceRestart the Hermes session or gateway if the newly installed skill is not visible immediately.
Install both the CLI binary and the focused OpenClaw skill. The installer defaults binaries to a per-user bin directory ($HOME/.local/bin on macOS/Linux, %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows):
npx -y @mvanhorn/printing-press-library install luma --agent openclawRestart the OpenClaw session or gateway if the newly installed skill is not visible immediately.
This CLI ships an MCPB bundle — Claude Desktop's standard format for one-click MCP extension installs (no JSON config required).
To install:
- Download the
.mcpbfor your platform from the latest release. - Double-click the
.mcpbfile. Claude Desktop opens and walks you through the install.
Requires Claude Desktop 1.0.0 or later. Pre-built bundles ship for macOS Apple Silicon (darwin-arm64) and Windows (amd64, arm64); for other platforms, use the manual config below.
Manual JSON config (advanced)
If you can't use the MCPB bundle (older Claude Desktop, unsupported platform), install the MCP binary and configure it manually.
go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/luma/cmd/luma-pp-mcp@latestAdd to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"luma": {
"command": "luma-pp-mcp"
}
}
}No account or API key required. luma reads Luma's public, read-only discovery API the website itself uses. It cannot create events, manage guests, or read private/subscribed calendars — that is the paid Luma Plus API's job.
# health check — confirms the public API is reachable
luma-pp-cli doctor --dry-run
# upcoming events in San Francisco
luma-pp-cli events list --city sf --limit 10
# list topic categories (AI, Crypto, Tech) and their ids
luma-pp-cli discover categories
# events for a category id from the list above
luma-pp-cli events list --category cat-ai --limit 10
# mirror a city's events locally so search/digest/drift work offline
luma-pp-cli sync --resources events --resource-param events:slug=sf
# offline full-text search across everything synced
luma-pp-cli search "summit"
These capabilities aren't available in any other tool for this API.
-
agenda— One flat, date-sorted list of upcoming events across multiple cities and categories at once.Reach for this when the user asks 'what AI events are on this week' across several cities — no single Luma call can answer it.
luma-pp-cli agenda --city sf --city nyc --category cat-ai --window 7d --agent
-
near— Find events within N km of a lat/lng, ranked by distance.Use when the user wants events near a point or venue, which no Luma API call supports.
luma-pp-cli near --lat 37.77 --lng -122.42 --radius-km 5 --window 14d --agent
-
ics— Export a synced/filtered set of events to a .ics calendar file your calendar app can import.Use when the user wants events on their own calendar instead of re-reading JSON.
luma-pp-cli ics --city sf --category cat-ai --window 30d --out ai.ics
-
watch— Show what changed on synced events since the previous sync — new, removed, filling up, sold out, rescheduled.Reach for this to monitor events over time; a single API call can never show change.
luma-pp-cli watch --city sf --category cat-ai --agent
-
calendars compare— Side-by-side upcoming-event counts and total guest counts across several calendars (communities).Use to benchmark which communities are most active or drawing the biggest crowds.
luma-pp-cli calendars compare cal-AAA cal-BBB cal-CCC --window 14d --agent
luma-pp-cli events get --event-id evt-XXXX --agent --select api_id,event.name,event.start_at,event.timezone,guest_count,ticket_countEvent detail is large and deeply nested; --select pulls only the fields you need so an agent doesn't burn context.
luma-pp-cli agenda --city sf --city nyc --category cat-ai --window 7d --agentUnions several cities filtered to a category into one flat, date-sorted list the API can't return.
luma-pp-cli near --lat 37.77 --lng -122.42 --radius-km 5 --window 14d --agentHaversine radius search over synced event coordinates — no Luma endpoint offers this.
luma-pp-cli ics --city sf --out sf.icsWrites an ICS file you can import into any calendar app.
Run luma-pp-cli --help for the full command reference and flag list.
Fetch Luma calendar (community) details
luma-pp-cli calendars- Get a calendar (community) by its api_id (cal-...)
Discover featured events, places, and categories on Luma
luma-pp-cli discover categories- List event categories (AI, Crypto, Tech, Arts, ...) with upcoming-event countsluma-pp-cli discover home- Featured place, popular places, categories, and calendars on the Luma discover home
Browse and fetch public Luma events
luma-pp-cli events get- Get full details for an event by its api_id (evt-...)luma-pp-cli events list- List upcoming events filtered by city (--city/--place-id) or category (--category)
Browse cities/places that host Luma events
luma-pp-cli places calendars- List calendars (communities) active in a placeluma-pp-cli places get- Get a place (city) by slug (sf, nyc, miami, ...) or place api_idluma-pp-cli places map- Geographic points for events in a place, for mapping
# Human-readable table (default in terminal, JSON when piped)
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000
# JSON for scripting and agents
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000 --json
# Filter to specific fields
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000 --json --select id,name,status
# Dry run — show the request without sending
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000 --dry-run
# Agent mode — JSON + compact + no prompts in one flag
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000 --agentThis CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--jsonoutput to stdout, errors to stderr - Filterable -
--select id,namereturns only fields you need - Previewable -
--dry-runshows the request without sending - Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
- Offline-friendly - sync/search commands can use the local SQLite store when available
- Agent-safe by default - no colors or formatting unless
--human-friendlyis set
Exit codes: 0 success, 2 usage error, 3 not found, 5 API error, 7 rate limited, 10 config error.
luma-pp-cli doctorVerifies configuration and connectivity to the API.
Config file: ~/.config/luma-pp-cli/config.toml
Static request headers can be configured under headers; per-command header overrides take precedence.
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
listcommand to see available items
- events near / search / digest / drift return nothing — Run sync first (e.g. luma-pp-cli sync --resources events --resource-param events:slug=sf) — these commands read the local store.
- unknown city returns empty — Use a real Luma city slug (sf, nyc, miami, london); run luma-pp-cli discover home to see places.
- HTTP 429 / rate limited — Lower --limit or add --max-scan-pages; the public API throttles aggressive paging.
This CLI was built by studying these projects and resources:
- luma-events-mcp — TypeScript
- Lu.Ma .NET SDK — C#
- luma-ai-mcp-server — TypeScript
Generated by CLI Printing Press