Luma
Connect Luma to create events, manage guests, tickets and coupons, send invites and email blasts, and work with your calendar's contacts.
Nothing has to be typed into PopMCP. You click Authorize with Luma, sign in to Luma and approve PopMCP. There is no developer app or callback URL to set up, and any Luma account works. Under More options you can use an API key instead, from a calendar on Luma Plus, for webhooks, cancelling events and organization tools.
- Setup time
- 1 min
- Auth
- OAuth authorization
- API base URL
- https://mcp.luma.com
Before you begin
- A Luma account that manages the events or calendars you want to work with
- Pop-up blockers must allow the Luma sign-in window to open
- Only for the API key route: Luma Plus on the calendar
- Only if the AI should change anything: an owner or admin in PopMCP to allow write actions
Get your credentials
Start the connection from PopMCP
Open the Luma connector in PopMCP and click Authorize with Luma. There are no fields to fill in: no API key, no developer app and nothing to register.
Sign in to Luma and approve
The window opens on luma.com. Sign in with the account that manages your events if you are not signed in already, then click Authorize. Luma may show an Unverified App notice with PopMCP's address, because it has not reviewed the app. Your AI will see what this account can see in Luma, and changes are made as this account.
PopMCP is requesting access
Once authorized, PopMCP will be able to view and manage your events, calendars, and guest lists on your behalf.
Use an API key instead, if you need one
Optional, and only if you need webhooks, cancelling events or organization tools. It needs Luma Plus on the calendar. Open luma.com/calendar/manage/api-keys, choose the calendar, generate an API key and copy it. Back in PopMCP, open More options, paste it into API key and connect. A key replaces signing in, and each key reaches only the calendar it was made on.
Manage API Keys
Your API Keys give you API access to events that are managed by the calendar. Luma Plus is required to use the API.
This key grants full access to the calendar, so treat it like a password.
Check it is connected
The Luma card in PopMCP reads Connected. New connections start read-only, so anything that changes Luma or contacts your guests waits until an owner or admin allows write actions in PopMCP.
Luma
- Status
- Connected
- Account
- you@example.com
- Access
- Read only
Connect in PopMCP
Open your workspace, choose Luma in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| How you connectpreset | Click Authorize, sign in to Luma and approve. There is nothing to copy or paste, and it works on any Luma account. |
| API key (for webhooks, cancelling events and organizations)secret | Optional, and it replaces signing in. Needs Luma Plus on the calendar. In Luma: open your calendar, Settings, Developer, then generate a key and copy it. A key reaches one calendar. Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Luma immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Luma card in PopMCP shows Connected. Asking the AI for the connection profile (luma_connection_profile) shows how it is connected and what it can reach, and asking for your upcoming events returns them rather than an authorization error.
Troubleshooting
The sign-in window never opens
Why: A pop-up blocker is stopping the Luma window.
Fix: Allow pop-ups for PopMCP in your browser and click Authorize with Luma again.
Luma shows Page Not Found instead of the approval page
Why: Luma has to read PopMCP's sign-in details from its address, and could not reach them. This happens on a private or local PopMCP address.
Fix: Connect from your public PopMCP address, or use an API key under More options.
"Your Luma sign-in has ended"
Why: The sign-in expired, or PopMCP's access was removed in Luma.
Fix: Reconnect Luma in PopMCP. It takes one click and a sign-in.
"Luma did not accept this API key"
Why: The key was copied in part, or it was deleted or replaced.
Fix: Copy it again from your calendar's Developer settings in Luma, or generate a new one.
"Luma refused this API key"
Why: API keys need Luma Plus on the calendar.
Fix: Upgrade the calendar in Luma, or connect by signing in, which needs no plan.
The AI says a tool needs an API key connection
Why: Webhooks, cancelling events and organization tools are only on Luma's API.
Fix: Reconnect Luma with an API key from a calendar on Luma Plus, under More options.
Luma answers 429
Why: Luma allows 200 requests a minute per calendar, and 500 for an organization key. Going over blocks the key for one minute.
Fix: Wait a minute, then try again with a narrower request.