Luma MCP Server

Connect Luma to Claude, ChatGPT, and other AI assistants so they can find events and manage the ones you host

Luma’s MCP server lets AI assistants like Claude and ChatGPT search Luma during a conversation. Ask “find AI hackathons in San Francisco this month”, “any run clubs near Williamsburg this weekend?”, or “what am I going to next week?” and the assistant pulls real events from Luma instead of guessing.

It can also manage the events you host. Ask “how many people are approved for my dinner on Thursday?”, “approve everyone from acme.com”, “create a happy hour next Friday at 6pm and invite last month’s speakers”, “invite Julia to Thursday’s dinner”, or “remind everyone going that doors open at 7” without opening your dashboard.

MCP (the Model Context Protocol) is an open standard for connecting AI apps to tools and data. Luma’s server lives at:

https://mcp.luma.com

Anyone with a Luma account can connect — you don’t need Luma Plus.

What It Can Do

Look things up:

Event and calendar links — look up a Luma URL or slug so the assistant can find the event or calendar you mean
Discover events — search upcoming public events on Luma by keyword, location, and date range
Your events — list what you’re attending or hosting, upcoming or past, with the location and meeting details you have access to
Events you manage — full details for any event you manage: settings, hosts, ticket types, guest counts by status, and payment summary
Calendar events — list the events on a calendar you manage, including ones you don’t personally host, and any pending submissions
Guests — list the guests on an event you manage, filter by approval status, search by name or email, and look up a single guest’s registration and tickets
Calendars — list the calendars you manage and get their details
Calendar contacts — search your calendar’s audience by name or email, discover and filter by contact tags, filter by membership, and sort by join date, registrations, check-ins, or revenue
People you know — find someone to invite by name or email, or list your closest connections as a starting guest list. People are ranked by how connected you are: co-hosting, chatting, and attending each other’s events. Only members of calendars you manage and contacts you’ve imported are visible, the same as the invite dialog on the dashboard.

Manage events you host:

Create and update events — set the name, time, location or meeting link, description, capacity, visibility, waitlist, and registration settings. Require phone numbers, collect first and last names separately, and enable group registration. Pick a cover image from Luma’s gallery and set the theme, font, and accent color. Custom event URLs and enabling separate first and last name fields require Luma Plus on the event’s calendar. When the time or location changes, guests get a push notification, but they’re only emailed if you ask the assistant to email them.
Guests — approve, decline, or waitlist registrations, and send invites by email or by naming someone you know. Invites count against your calendar’s send limit, the same as from the dashboard.
Ticket types — add, edit, and delete ticket types.
Hosts — add a co-host or check-in staff by email, change a host’s access or whether they’re shown on the event page, and remove hosts.
Blasts — email your guests now or on a schedule, choose who gets it by status or ticket type, and review, edit, reschedule, or delete blasts. Blasts count against your calendar’s send limit, the same as from the dashboard.

Manage calendars:

Event submissions — see who submitted each event, approve pending submissions, or reject them with an optional message to the submitter
Calendar profile — update a team calendar’s name, description, avatar, or color
Calendar status — switch a team calendar between Active, Coming Soon, and Archived. Coming Soon shows a placeholder page; Archived stops new follows and visitor event submissions.

Most AI apps ask you to confirm before the assistant makes a change. Things the assistant can’t do: create calendars, invite calendar admins, cancel events, refund a guest without changing their status, or change your account settings. Use the dashboard for those.

The assistant only sees what you can see. For an event you manage, it gets the same data as your manage dashboard. For an event you’re attending, it gets the guest-facing details. If you share a private event link, the assistant can look up its basic page information, such as its name, cover, and times. Guest lists, private locations, and management tools still require the appropriate access.

Connecting to Claude

Claude web and desktop apps (Pro, Max, Team, or Enterprise plan):

Luma is in Claude’s connector directory:

Open claude.ai/directory/luma — or find Luma under Settings → Connectors → Browse connectors
Click Connect — a Luma window opens
Sign in to Luma if needed and click Authorize

On Team and Enterprise plans, an owner enables the Luma connector for the organization first, and each member connects their own Luma account after that.

To use it in a chat, click the + button, choose Connectors, and make sure Luma is toggled on.

Claude Code:

claude mcp add --transport http luma https://mcp.luma.com

Then run /mcp and choose Luma to sign in.

Connecting to ChatGPT

Luma is in ChatGPT’s app directory:

Open Luma’s listing — or search for Luma at chatgpt.com/plugins
Click Connect — sign in to Luma if needed and click Authorize
In a chat, just mention Luma (“find AI events on Luma this weekend”) — or open the + menu and choose Luma

In Business, Enterprise, and Edu workspaces, apps can be turned off by the workspace admin. If the Connect button says it’s disabled, ask your admin to enable Luma under Workspace settings → Apps.

Other MCP Clients

Clients that support remote MCP servers over streamable HTTP and OAuth Client ID Metadata Documents will work, including Codex and Grok. Point your client at https://mcp.luma.com and it will walk you through signing in to Luma. No API key or manual token setup is needed.

Luma doesn’t support OAuth dynamic client registration and doesn’t issue client IDs or secrets for the MCP server. Clients that can only connect that way won’t work.

Access and Privacy

Connecting grants the AI app access to your Luma account — the same events, guests, and calendars you can see and manage when signed in. Changes the assistant makes are made as you.
Results from these tools end up in your AI chat transcript. If you manage events with sensitive guest lists, keep that in mind before asking an assistant to pull them.
Luma admin permissions don’t carry over. Even Luma staff only see events they personally host or manage through MCP.
To disconnect, remove the Luma connector in Claude, ChatGPT, or whichever client you added it to.

Troubleshooting

If a connection isn’t working, check that you’re signed in to the right Luma account, then remove the connector and add it again.

“Dynamic client registration failed”

Your client is trying to register itself using OAuth dynamic client registration, which Luma doesn’t support. Luma’s MCP server uses Client ID Metadata Documents instead. Some automation tools, like n8n, only support dynamic registration and can’t connect to Luma’s MCP server. We don’t provide manual client IDs, client secrets, or callback URL allowlisting as an alternative.

If you’re building an integration rather than chatting with an assistant, the Luma API is probably what you want.