Skip to content
actionlake
Start free

Connectors · Marketing & media

Luma MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Luma and the rest of your systems. It gives your agent 74 Luma actions (26 reads, 38 writes and 10 that wait for a confirmation) and holds the Luma credential itself, so the agent never does. It paces Luma's limits and records every call.

Connect Luma freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "luma.calendar_events.list",  intent: "check which Luma account is connected"}# List calendar events · read · 1 upstream call
  • 74actionsin one signed file
  • 26readlook, never change
  • 38writecreate and update
  • 10wait for a yesdestructive, confirmed first

Set up

Connect Luma in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Luma.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyLuma API key: in Luma open your calendar > Settings > Developer and create an API key (needs Luma Plus)
    account { op: "connections.requirements", service: "luma" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "luma.calendar_events.list" }# list calendar events · read · 1 upstream callcheck { action: "luma.events.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Luma at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
200 calls a minute, per connection
API covered
Luma API 1.0.0 (OpenAPI 3.1.0)public-api.luma.com
Built from
Luma's documentation, read 23 October 2026public-api.luma.comdocs.luma.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
26 of 26 reads, for up to 5 minutes; a write clears what it affects
Shared entities
6, so ask can line Luma up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Luma.

74 actions in 23 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 26readlook, never change
  • 38writecreate and update
  • 10destructivewait for a confirmation

  1. Contact tags

    6

    1 read · 4 write · 1 destructive

    List contact tags · Create contact tag · Update contact tag · Delete contact tag

  2. Event tags

    6

    1 read · 4 write · 1 destructive

    Create event tag · List event tags · Apply event tag · Unapply event tag

  3. Guests

    6

    2 read · 4 write · 0 destructive

    List guests · Get guest · Update guest status · Add guests

  4. Blasts

    5

    2 read · 2 write · 1 destructive

    Create blast · List blasts · Get blast · Update blast

  5. Calendar events

    5

    2 read · 3 write · 0 destructive

    List calendar events · Add event to calendar · Approve event submission · Look up event on calendar

  6. Contacts

    5

    1 read · 3 write · 1 destructive

    List calendar contacts · Remove contact · Restore contact · Import contacts

  7. Events

    5

    1 read · 3 write · 1 destructive

    Create event · Get event · Update event · Cancel event

  8. Ticket types

    5

    2 read · 2 write · 1 destructive

    Create ticket type · List ticket types · Get ticket type · Update ticket type

15 more areas · 31 actions
  • Webhooks 5
  • Calendar coupons 3
  • Event coupons 3
  • Hosts 3
  • Calendar admins 2
  • Calendars 2
  • Images 2
  • Membership members 2
  • Organization calendars 2
  • Organization events 2
  • Entities 1
  • Membership tiers 1
  • Organization admins 1
  • Places 1
  • Users 1

Top actions

The Luma API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 31 of Luma's 31 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
luma.calendar_events.listList calendar eventsEvery event and API key on Luma is managed by a [Luma Calendar](https://help.luma.com/p/luma-calendar-overview).readcomm.event.list61 connectors
luma.contacts.listList calendar contactsList Contacts.readcrm.contact.list177 connectors
luma.guests.listList guestsGet list of guests who have registered or been invited to an event.readcomm.audience_member.list23 connectors
luma.events.createCreate eventCreate Event.writecomm.event.create52 connectors
luma.calendar_admins.listList calendar adminsList all admins for the calendar.readidentity.user.list474 connectors
luma.events.updateUpdate eventUpdate Event.writecomm.event.update53 connectors
luma.contact_tags.listList contact tagsList Contact Tags.readcrm.tag.list65 connectors
luma.organization_calendars.listList organization calendarsList all calendars belonging to the organization.readcomm.calendar.list14 connectors
luma.contacts.removeRemove contactRemove a contact from your calendar.destructivecrm.contact.delete147 connectors
luma.guests.getGet guestGet detailed information for an event guest by looking them up by their ID.readcomm.audience_member.get17 connectors
luma.calendars.getGet calendarGet information about the calendar.readcomm.calendar.get12 connectors
luma.contact_tags.createCreate contact tagCreate Contact Tag.writecrm.tag.create49 connectors

Try it

Prompts to paste into Claude.

Each one names the Luma actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Find the Luma contacts with no email address, so we can clean them up.

    callsluma.contacts.list

  2. Writewrite

    Create event in Luma. Show me exactly what you will send before you save it.

    callsluma.events.create

  3. Across systemsread

    Which contacts are in both Luma and HaloPSA, and how many are in only one of them?

    callsluma.contacts.listhalopsa.users.list

Across your systems

Luma, joined to the rest of your business.

One ask fetches from Luma and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which contacts are in both Luma and HaloPSA, and how many are in only one of them?

    luma.contacts.list + halopsa.users.list, on crm.contact · HaloPSA

  • Which contacts are in both Luma and NetSuite, and how many are in only one of them?

    luma.contacts.list + netsuite.views.contacts, on crm.contact · NetSuite

Also mapped by other connectorsidentity.user 517crm.contact 192comm.event 47crm.tag 47comm.audience_member 16comm.calendar 8
ask
ask {  intent: "which contacts are in both Luma and HaloPSA, and how many are in only one of them",  steps: [    { action: "luma.contacts.list", as: "people", input: {}, limit: 100, max_pages: 5 },    { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "people",        right: "people2",        on: "crm.contact",        group_by: "people.email",        select: ["people.email", "count(people2.id) as in_halopsa"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Luma

Destructive actions wait for a yes.

10 Luma actions are destructive. These are all of them:

  • Remove contactluma.contacts.remove
  • Cancel eventluma.events.cancel
  • Delete contact tagluma.contact_tags.delete
  • Delete webhookluma.webhooks.delete
  • Add calendar adminsluma.calendar_admins.add
  • Transfer event to another calendarluma.organization_events.transfer_calendar
  • Remove event hostluma.hosts.remove
  • Delete blastluma.blasts.delete
  • Delete event tagluma.event_tags.delete
  • Delete ticket typeluma.ticket_types.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doluma.contacts.removeconfirm_policy: human

Remove contact?

intent: the user asked me to remove contact

run suspended · waiting for a named person · key luma-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "luma-agent",  allowed_actions: ["luma.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "luma.contacts.remove", approver: "[email protected]" },    { match: "luma.events.cancel", approver: "[email protected]" },    { match: "luma.contact_tags.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Luma only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Luma costs on actionlake.

Every Luma action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Luma refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 74 Luma actions
  • 74actions pageeach page of a long list is one call
  • 26reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Luma action.

74 actions by area: the id your agent calls, what it does, and its effect.

Contact tags6
  • luma.contact_tags.applyApply contact tagwrite
  • luma.contact_tags.createCreate contact tagwrite
  • luma.contact_tags.deleteDelete contact tagdestructive
  • luma.contact_tags.listList contact tagsread
  • luma.contact_tags.unapplyUnapply contact tagwrite
  • luma.contact_tags.updateUpdate contact tagwrite
Event tags6
  • luma.event_tags.applyApply event tagwrite
  • luma.event_tags.createCreate event tagwrite
  • luma.event_tags.deleteDelete event tagdestructive
  • luma.event_tags.listList event tagsread
  • luma.event_tags.unapplyUnapply event tagwrite
  • luma.event_tags.updateUpdate event tagwrite
Guests6
  • luma.guests.addAdd guestswrite
  • luma.guests.getGet guestread
  • luma.guests.listList guestsread
  • luma.guests.send_invitesSend event inviteswrite
  • luma.guests.update_statusUpdate guest statuswrite
  • luma.guests.update_ticketsUpdate guest ticketswrite
Blasts5
  • luma.blasts.createCreate blastwrite
  • luma.blasts.deleteDelete blastdestructive
  • luma.blasts.getGet blastread
  • luma.blasts.listList blastsread
  • luma.blasts.updateUpdate blastwrite
Calendar events5
  • luma.calendar_events.addAdd event to calendarwrite
  • luma.calendar_events.approveApprove event submissionwrite
  • luma.calendar_events.listList calendar eventsread
  • luma.calendar_events.lookupLook up event on calendarread
  • luma.calendar_events.rejectReject event submissionwrite
Contacts5
  • luma.contacts.blockBlock contactwrite
  • luma.contacts.importImport contactswrite
  • luma.contacts.listList calendar contactsread
  • luma.contacts.removeRemove contactdestructive
  • luma.contacts.restoreRestore contactwrite
Events5
  • luma.events.cancelCancel eventdestructive
  • luma.events.createCreate eventwrite
  • luma.events.getGet eventread
  • luma.events.request_cancellationRequest event cancellation tokenwrite
  • luma.events.updateUpdate eventwrite
Ticket types5
  • luma.ticket_types.createCreate ticket typewrite
  • luma.ticket_types.deleteDelete ticket typedestructive
  • luma.ticket_types.getGet ticket typeread
  • luma.ticket_types.listList ticket typesread
  • luma.ticket_types.updateUpdate ticket typewrite
Webhooks5
  • luma.webhooks.createCreate webhookwrite
  • luma.webhooks.deleteDelete webhookdestructive
  • luma.webhooks.getGet webhookread
  • luma.webhooks.listList webhooksread
  • luma.webhooks.updateUpdate webhookwrite
Calendar coupons3
  • luma.calendar_coupons.createCreate calendar couponwrite
  • luma.calendar_coupons.listList calendar couponsread
  • luma.calendar_coupons.updateUpdate calendar couponwrite
Event coupons3
  • luma.event_coupons.createCreate event couponwrite
  • luma.event_coupons.listList event couponsread
  • luma.event_coupons.updateUpdate event couponwrite
Hosts3
  • luma.hosts.addAdd event hostwrite
  • luma.hosts.removeRemove event hostdestructive
  • luma.hosts.updateUpdate event hostwrite
Calendar admins2
  • luma.calendar_admins.addAdd calendar adminsdestructive
  • luma.calendar_admins.listList calendar adminsread
Calendars2
  • luma.calendars.getGet calendarread
  • luma.calendars.updateUpdate calendarwrite
Images2
  • luma.images.create_upload_urlCreate image upload URLwrite
  • luma.images.searchSearch cover imagesread
Membership members2
  • luma.membership_members.addAdd member to tierwrite
  • luma.membership_members.update_statusUpdate member statuswrite
Organization calendars2
  • luma.organization_calendars.createCreate calendar in organizationwrite
  • luma.organization_calendars.listList organization calendarsread
Organization events2
  • luma.organization_events.listList organization eventsread
  • luma.organization_events.transfer_calendarTransfer event to another calendardestructive
Entities1
  • luma.entities.lookupLook up event or calendar by slugread
Membership tiers1
  • luma.membership_tiers.listList membership tiersread
Organization admins1
  • luma.organization_admins.listList organization adminsread
Places1
  • luma.places.searchSearch placesread
Users1
  • luma.users.get_selfGet self (authenticated user)read

Questions

The Luma MCP server, answered.

Is there a Luma MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 74 Luma actions across contact tags, event tags, guests and blasts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Luma.

What do I need to connect Luma?

Luma API key: in Luma open your calendar > Settings > Developer and create an API key (needs Luma Plus). The free call account { op: "connections.requirements", service: "luma" } lists exactly what to paste.

Can an AI agent delete or change things in Luma?

Only if its key allows it, and only with an explicit confirmation. 10 Luma actions are destructive, including remove contact, cancel event and delete contact tag. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Luma API limit?

actionlake paces every call to the limits in the Luma service file: 200 calls a minute per connection. Repeated reads are answered from cache (26 Luma actions can be), which never reaches Luma.

What does a Luma action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (74 Luma actions page). Cache hits, searches, dry runs and calls Luma refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Luma API does it cover?

The Luma API 1.0.0 (OpenAPI 3.1.0) at public-api.luma.com. It is built from Luma's documentation as read on 23 October 2026. 74 actions in 23 areas, each one in the signed service file (version 1.0.0).

Can I combine Luma with my other systems?

Yes. ask joins Luma to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Luma maps crm.contact, which 192 other connectors also map.

Does actionlake keep my Luma data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Luma credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Luma

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Luma; the name is the vendor's own. Counts are from the Luma service file, version 1.0.0.

Give your agent Luma today.

Connect Luma freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.