---
title: "Luma MCP server for AI agents - actionlake"
description: "Give Claude 74 Luma actions through one MCP server: contact tags, event tags, guests, blasts. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/luma
updated: 2026-10-23
---

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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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
```

- 74 actions in one signed file
- 26 read look, never change
- 38 write create and update
- 10 wait for a yes destructive, 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_key` Luma 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 call
   check { 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 2026[public-api.luma.com](https://public-api.luma.com/openapi.json) [docs.luma.com](https://docs.luma.com/reference/getting-started-with-your-api)

**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.

- **26** read look, never change
- **38** write create and update
- **10** destructive wait 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.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `luma.calendar_events.list` List calendar events | Every event and API key on Luma is managed by a [Luma Calendar](https://help.luma.com/p/luma-calendar-overview). | read | `comm.event.list` 61 connectors |
| `luma.contacts.list` List calendar contacts | List Contacts. | read | `crm.contact.list` 177 connectors |
| `luma.guests.list` List guests | Get list of guests who have registered or been invited to an event. | read | `comm.audience_member.list` 23 connectors |
| `luma.events.create` Create event | Create Event. | write | `comm.event.create` 52 connectors |
| `luma.calendar_admins.list` List calendar admins | List all admins for the calendar. | read | `identity.user.list` 474 connectors |
| `luma.events.update` Update event | Update Event. | write | `comm.event.update` 53 connectors |
| `luma.contact_tags.list` List contact tags | List Contact Tags. | read | `crm.tag.list` 65 connectors |
| `luma.organization_calendars.list` List organization calendars | List all calendars belonging to the organization. | read | `comm.calendar.list` 14 connectors |
| `luma.contacts.remove` Remove contact | Remove a contact from your calendar. | destructive | `crm.contact.delete` 147 connectors |
| `luma.guests.get` Get guest | Get detailed information for an event guest by looking them up by their ID. | read | `comm.audience_member.get` 17 connectors |
| `luma.calendars.get` Get calendar | Get information about the calendar. | read | `comm.calendar.get` 12 connectors |
| `luma.contact_tags.create` Create contact tag | Create Contact Tag. | write | `crm.tag.create` 49 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. Read read
   Find the Luma contacts with no email address, so we can clean them up.
   calls `luma.contacts.list`
2. Write write
   Create event in Luma. Show me exactly what you will send before you save it.
   calls `luma.events.create`
3. Across systems read
   Which contacts are in both Luma and HaloPSA, and how many are in only one of them?
   calls `luma.contacts.list` `halopsa.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](https://actionlake.com/connectors/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](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `identity.user` **517** `crm.contact` **192** `comm.event` **47** `crm.tag` **47** `comm.audience_member` **16** `comm.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 contact `luma.contacts.remove`
- Cancel event `luma.events.cancel`
- Delete contact tag `luma.contact_tags.delete`
- Delete webhook `luma.webhooks.delete`
- Add calendar admins `luma.calendar_admins.add`
- Transfer event to another calendar `luma.organization_events.transfer_calendar`
- Remove event host `luma.hosts.remove`
- Delete blast `luma.blasts.delete`
- Delete event tag `luma.event_tags.delete`
- Delete ticket type `luma.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.

do luma.contacts.remove confirm_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: "lead@example.com" },
    { match: "luma.events.cancel", approver: "lead@example.com" },
    { match: "luma.contact_tags.delete", approver: "lead@example.com" }
  ]
}
```

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.

- 1 upstream call per action all 74 Luma actions
- 74 actions page each page of a long list is one call
- 26 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Luma action.

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

**Contact tags 6**

- `luma.contact_tags.apply` Apply contact tag write
- `luma.contact_tags.create` Create contact tag write
- `luma.contact_tags.delete` Delete contact tag destructive
- `luma.contact_tags.list` List contact tags read
- `luma.contact_tags.unapply` Unapply contact tag write
- `luma.contact_tags.update` Update contact tag write

**Event tags 6**

- `luma.event_tags.apply` Apply event tag write
- `luma.event_tags.create` Create event tag write
- `luma.event_tags.delete` Delete event tag destructive
- `luma.event_tags.list` List event tags read
- `luma.event_tags.unapply` Unapply event tag write
- `luma.event_tags.update` Update event tag write

**Guests 6**

- `luma.guests.add` Add guests write
- `luma.guests.get` Get guest read
- `luma.guests.list` List guests read
- `luma.guests.send_invites` Send event invites write
- `luma.guests.update_status` Update guest status write
- `luma.guests.update_tickets` Update guest tickets write

**Blasts 5**

- `luma.blasts.create` Create blast write
- `luma.blasts.delete` Delete blast destructive
- `luma.blasts.get` Get blast read
- `luma.blasts.list` List blasts read
- `luma.blasts.update` Update blast write

**Calendar events 5**

- `luma.calendar_events.add` Add event to calendar write
- `luma.calendar_events.approve` Approve event submission write
- `luma.calendar_events.list` List calendar events read
- `luma.calendar_events.lookup` Look up event on calendar read
- `luma.calendar_events.reject` Reject event submission write

**Contacts 5**

- `luma.contacts.block` Block contact write
- `luma.contacts.import` Import contacts write
- `luma.contacts.list` List calendar contacts read
- `luma.contacts.remove` Remove contact destructive
- `luma.contacts.restore` Restore contact write

**Events 5**

- `luma.events.cancel` Cancel event destructive
- `luma.events.create` Create event write
- `luma.events.get` Get event read
- `luma.events.request_cancellation` Request event cancellation token write
- `luma.events.update` Update event write

**Ticket types 5**

- `luma.ticket_types.create` Create ticket type write
- `luma.ticket_types.delete` Delete ticket type destructive
- `luma.ticket_types.get` Get ticket type read
- `luma.ticket_types.list` List ticket types read
- `luma.ticket_types.update` Update ticket type write

**Webhooks 5**

- `luma.webhooks.create` Create webhook write
- `luma.webhooks.delete` Delete webhook destructive
- `luma.webhooks.get` Get webhook read
- `luma.webhooks.list` List webhooks read
- `luma.webhooks.update` Update webhook write

**Calendar coupons 3**

- `luma.calendar_coupons.create` Create calendar coupon write
- `luma.calendar_coupons.list` List calendar coupons read
- `luma.calendar_coupons.update` Update calendar coupon write

**Event coupons 3**

- `luma.event_coupons.create` Create event coupon write
- `luma.event_coupons.list` List event coupons read
- `luma.event_coupons.update` Update event coupon write

**Hosts 3**

- `luma.hosts.add` Add event host write
- `luma.hosts.remove` Remove event host destructive
- `luma.hosts.update` Update event host write

**Calendar admins 2**

- `luma.calendar_admins.add` Add calendar admins destructive
- `luma.calendar_admins.list` List calendar admins read

**Calendars 2**

- `luma.calendars.get` Get calendar read
- `luma.calendars.update` Update calendar write

**Images 2**

- `luma.images.create_upload_url` Create image upload URL write
- `luma.images.search` Search cover images read

**Membership members 2**

- `luma.membership_members.add` Add member to tier write
- `luma.membership_members.update_status` Update member status write

**Organization calendars 2**

- `luma.organization_calendars.create` Create calendar in organization write
- `luma.organization_calendars.list` List organization calendars read

**Organization events 2**

- `luma.organization_events.list` List organization events read
- `luma.organization_events.transfer_calendar` Transfer event to another calendar destructive

**Entities 1**

- `luma.entities.lookup` Look up event or calendar by slug read

**Membership tiers 1**

- `luma.membership_tiers.list` List membership tiers read

**Organization admins 1**

- `luma.organization_admins.list` List organization admins read

**Places 1**

- `luma.places.search` Search places read

**Users 1**

- `luma.users.get_self` Get 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

- [Kit 12](https://actionlake.com/connectors/kit)
- [Circle 11](https://actionlake.com/connectors/circle)
- [Livestorm 10](https://actionlake.com/connectors/livestorm)
- [Calendly 10](https://actionlake.com/connectors/calendly)
- [Cvent 10](https://actionlake.com/connectors/cvent)
- [Mighty Networks 6](https://actionlake.com/connectors/mighty-networks)

Joins with, on shared entities

- [Odoo 4](https://actionlake.com/connectors/odoo)
- [HighLevel (LeadConnector) 4](https://actionlake.com/connectors/highlevel-leadconnector)
- [Clio Manage 4](https://actionlake.com/connectors/clio-manage)
- [HaloPSA 3](https://actionlake.com/connectors/halopsa)
- [Salesforce Sales Cloud 3](https://actionlake.com/connectors/salesforce-sales-cloud)
- [Planning Center 3](https://actionlake.com/connectors/planning-center)

Browse

- [All Marketing & media connectors](https://actionlake.com/connectors/category/marketing-and-media)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

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

---

Source: https://actionlake.com/connectors/luma
More: https://actionlake.com/llms.txt