100+ integrations are ready to connect to your AI.Connect your first MCP

Luma MCP server for your AI

Create an event, see who is going, approve the waitlist, invite your contacts, make a discount code or email your guests, all by asking.

PopMCPLuma

Who is going to my next event, and who is still waiting for approval?

Supported Luma tools

Sign in and your AI gets the tools Luma offers signed-in accounts, on any Luma account. An API key from a calendar on Luma Plus gives it every endpoint of Luma's API instead, which is the list on this page, including webhooks, cancelling events and organization tools. A few tools do a whole job at once: finding an event by name, one event at a glance, and everyone on a guest list.

78 tools in the full catalog: 29 read and 49 write. 38 load by default, and the rest are found with tool search.

luma_apply_contact_tag

Tag existing contacts.

luma_apply_event_tag

Tag events on the calendar.

luma_list_contact_tags

List the calendar's contact tags, with their ids.

luma_list_event_tags

List the calendar's event tags, with their ids.

luma_approve_calendar_event

Approve an event waiting on this calendar, from luma_list_events with status=pending.

luma_get_calendar

Get the connected calendar's name, url, status, location, social links and event defaults.

luma_list_events

List the events on the connected Luma calendar, soonest or latest first.

luma_add_guests

Register people on an event straight away, as going unless approval_status says otherwise.

luma_cancel_event

Step 2 of cancelling an event.

luma_create_event

Create an event on the connected calendar.

luma_event_overview

One event with its ticket types, coupons and guest counts by status.

luma_export_guests

Everyone on an event, across pages, with counts by status.

luma_find_events

Find events on the calendar by part of their name.

luma_get_event

Get one event in full: time, location, description, capacity, registration questions, hosts.

luma_get_guest

Get one guest with their answers, tickets and orders.

luma_list_guests

List an event's guests with name, email, status and tickets, one page at a time.

luma_request_event_cancellation

Step 1 of cancelling an event.

luma_send_invites

Email an invitation to an event, and an SMS when their phone is linked.

luma_update_event

Change an event.

luma_update_guest_status

Approve, decline, waitlist or set a guest back to pending.

luma_update_guest_tickets

Give a guest complimentary tickets or invalidate some they hold, with no charge.

luma_create_event_coupon

Create a discount code for one event.

luma_list_event_coupons

List all coupons that have been created for an event.

luma_lookup_entity

Turn a Luma URL or slug into an event or calendar.

luma_search_cover_images

Search Luma's stock cover images by keyword.

luma_search_places

Search Google Maps for a place, up to 5 candidates.

luma_upload_image

Put a picture on Luma's image host, ready to use as an event cover.

luma_create_blast

Email a message to an event's guests, now or at scheduled_for.

luma_create_ticket_type

Add a ticket type to an event.

luma_create_webhook

Have Luma call a URL when something happens on this calendar.

luma_import_contacts

Add people to the calendar's contacts.

luma_list_blasts

List the blasts (emails to guests) on an event, newest first.

luma_list_contacts

List or search the calendar's contacts.

luma_list_ticket_types

List all ticket types for an event

luma_list_webhooks

List this calendar's webhooks.

luma_update_ticket_type

Update an existing ticket type configuration

luma_add_host

Add a host or check-in staff member to an event by email.

luma_list_membership_tiers

List the calendar's membership tiers, including hidden ones.

luma_create_contact_tag

Create a contact tag.

luma_create_event_tag

Create an event tag.

luma_delete_contact_tag

Delete a contact tag.

luma_delete_event_tag

Delete an event tag.

luma_unapply_contact_tag

Take a tag off contacts.

luma_unapply_event_tag

Unapply a tag from events on the calendar.

luma_update_contact_tag

Rename or recolor a contact tag.

luma_update_event_tag

Rename or recolor an event tag.

luma_add_calendar_admins

Give people admin access to the calendar by email, at most 20 at a time.

luma_add_calendar_event

Put an existing event on this calendar.

luma_list_calendar_admins

List all admins for the calendar.

luma_lookup_calendar_event

See if an event already exists on the calendar.

luma_reject_calendar_event

Reject an event waiting on this calendar.

luma_update_calendar

Change the connected calendar's settings.

luma_create_calendar_coupon

Create a discount code usable on every event this calendar manages.

luma_create_image_upload_url

Get an one-time upload URL for an image (image/jpeg or image/png).

luma_get_self

Say who owns this connection: their user id, name and email.

luma_list_calendar_coupons

List all coupons that have been created for a calendar.

luma_update_calendar_coupon

Change a calendar coupon's remaining uses or valid dates.

luma_update_event_coupon

Change an event coupon's remaining uses or valid dates.

luma_block_contact

Block a contact so they can't follow your calendar or join its events.

luma_create_organization_calendar

Create a calendar in the organization.

luma_delete_blast

Delete a blast.

luma_delete_ticket_type

Soft delete a ticket type.

luma_delete_webhook

Delete a webhook endpoint.

luma_get_blast

Get a blast by ID.

luma_get_ticket_type

Get a single ticket type by ID

luma_get_webhook

Get one webhook by id, from luma_list_webhooks.

luma_list_organization_admins

List the organization's admins.

luma_list_organization_calendars

List every calendar in the organization.

luma_list_organization_events

List events across every calendar in the organization, without duplicates.

luma_remove_contact

Remove a contact from your calendar.

luma_restore_contact

Restore a blocked or removed contact, returning them to your active contacts.

luma_transfer_event_calendar

Move an event to another calendar in the same organization.

luma_update_blast

Edit a blast.

luma_update_webhook

Update a webhook endpoint's event types or status (active/paused).

luma_add_member_to_tier

Add an user to a membership tier.

luma_remove_host

Remove a host from an event.

luma_update_host

Update a host's permissions or visibility on an event.

luma_update_member_status

Update a member's membership status.

Connect Luma to Claude, ChatGPT and Claude Code

Authorize once, then an endpoint your client signs into. Nothing to deploy, and nothing to install on the Luma side.

Open Luma in PopMCP, click Authorize with Luma, sign in to Luma and approve. There is no developer app and no callback URL to set up, and any Luma account works. For webhooks, cancelling events and organization tools, add an API key from a calendar on Luma Plus under More options instead of signing in.

How you connectyour-luma-value
API key (for webhooks, cancelling events and organizations)••••••••••••3f7a
Authorize PopMCP on LumaAuthorize

Then just ask for the work

  • “Who is going to my next event, and who is still waiting for approval?”

    • list_events
    • export_guests
  • “Create a founders dinner on December 4 at 6pm New York time at Soho House, with 40 spots and approval required”

    • search_places
    • create_event
    • create_ticket_type
  • “Invite everyone tagged VIP to the founders dinner, and show me the list before anything goes out”

    • list_contacts
    • find_events
    • send_invites
  • “Make a 20% discount code for this event that the first 50 people can use”

    • find_events
    • create_event_coupon
  • “Email everyone going to tomorrow's event with the parking details, once I have read the message”

    • find_events
    • create_blast
  • “How did this event do? Tickets, guest counts and how many people actually checked in”

    • event_overview

Use Luma from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Luma MCP server questions

What teams ask before putting Luma behind an AI client.

Do I need Luma Plus?

Not to sign in. Luma says any Luma account can connect this way. Luma's API keys do need Luma Plus on the calendar, and a few features, such as custom event URLs, depend on the calendar's plan whichever way you connect.

Should I sign in or use an API key?

Sign in unless you need something only the API offers: webhooks, cancelling events, or organization tools. Signing in acts as you, across what you manage in Luma. An API key reaches one calendar, or a whole organization with an organization key.

Why does Luma call PopMCP an unverified app?

Luma shows that notice on its approval page for apps it has not reviewed. Check that the address on the page is PopMCP's, then approve.

Can the AI email my guests by itself?

Only if write actions are allowed in PopMCP, and new connections start read-only. Invites and blasts reach real people, count against your calendar's send limits, and a sent blast cannot be recalled, so the tools tell the AI to show you the list and the message first.

Can it cancel an event?

With an API key, yes, in two steps. The first shows how many guests are going and whether they paid and changes nothing; the second cancels the event, tells every guest and can refund them. It cannot be undone, so the AI is told to ask you between the two.

Does the AI see my guests' personal details?

It sees names, emails and registration answers for events you manage, because that is the job, and whatever it reads is saved in your AI chat. On an API key connection, check-in codes are never passed to it, and phone numbers stay out of guest lists unless it looks up one person.

Do I have to run or host the Luma MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect Luma to Claude Code?

Connect Luma in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Luma on the consent screen. The Luma tools are then available in that session, and no Luma credential is stored on your machine.

Why do only 38 of the 78 tools load by default?

Loading 78 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 38-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 78 here. A trigger is something PopMCP watches for you: 11 Luma events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Luma.

Connect Luma to your AI in minutes

Launch a hosted MCP endpoint for Luma, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP