Luma MCP integration for AI agents.
Connect AI agents to Luma through 6 structured actions, including get calendar, get event, and get event guest. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Luma integration exposes
The Luma Agent App exposes 6 provider-backed actions for productivity and social work. Its current contract lets an authorized agent get the luma calendar scoped to the current api key, get full details for a luma event the api key can manage, and get detailed information for a luma event guest. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Luma account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Luma capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_calendarREADGet the Luma calendar scoped to the current API key.
get_eventREADGet full details for a Luma event the API key can manage.
INPUTS: event_id
get_event_guestREADGet detailed information for a Luma event guest.
INPUTS: event_id / id
get_selfREADGet the Luma user profile for the current API key.
list_calendar_eventsREADList events for the Luma calendar scoped to the current API key.
INPUTS: before / after / pagination_cursor / pagination_limit / platforms
list_event_guestsREADList registered or invited guests for a Luma event.
INPUTS: event_id / approval_status / pagination_cursor / pagination_limit / sort_column
INPUT CONTRACTS
Know what the action needs before it runs.
get_event
event_idOPTIONAL- Luma event ID, usually starting with evt-.
get_event_guest
event_idOPTIONAL- Luma event ID, usually starting with evt-.
idOPTIONAL- Guest identifier: guest ID, ticket key, guest key, or email address.
list_calendar_events
beforeOPTIONAL- ISO 8601 date-time accepted by Luma, for example 2022-10-19T03:27:13.673Z.
afterOPTIONAL- ISO 8601 date-time accepted by Luma, for example 2022-10-19T03:27:13.673Z.
pagination_cursorOPTIONAL- Cursor token returned as next_cursor by a previous Luma page.
pagination_limitOPTIONAL- Maximum number of records to return. Luma enforces its own maximum.
platformsOPTIONAL- Event platforms to include, such as luma or external.
list_event_guests
event_idREQUIRED- Luma event ID, usually starting with evt-.
approval_statusOPTIONAL- Guest approval status to include.
pagination_cursorOPTIONAL- Cursor token returned as next_cursor by a previous Luma page.
pagination_limitOPTIONAL- Maximum number of records to return. Luma enforces its own maximum.
sort_columnOPTIONAL- The Luma guest sort column.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Calendar
Get the Luma calendar scoped to the current API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_calendarVerify with Get Event
Get full details for a Luma event the API key can manage. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_eventSAFETY BOUNDARY
Operate Luma with explicit limits
- Authorize Luma with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Luma data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Luma rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Luma task completed successfully.
CONNECTION MODEL
API key
Luma API key sent with the x-luma-api-key header. Generate a key for a calendar from the Luma calendar API key settings at https://luma.com/calendar/manage/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Luma.