Skip to main content
Glama
luma-events-mcp

luma-events-mcp

by montaguegabe

Luma Events MCP Server

An MCP server for the Luma Events API. Create, update, and manage events and guests.

Current Status

This server works well for managing and tweaking existing events. However, event creation has limited options—some settings like registration mode (approval required vs. open registration) aren't yet exposed. Event duplication is also not currently supported.

Contributions welcome to expand the available event settings.

Related MCP server: Pulumi Events MCP

Requirements

Development

uv run mcp dev luma.py

Installation

Add to your MCP client config:

{
  "mcpServers": {
    "luma-events": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/luma",
        "run",
        "python",
        "-m",
        "luma"
      ],
      "env": {
        "LUMA_API_KEY": "your-api-key"
      }
    }
  }
}

Available Tools

9 tools
add_hostA

Add a host to a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")
    email: Email address of the host to add
    name: Name of the host (ignored if they already have a Luma profile)

Returns:
    Result of adding host or an error message

Inputs: email (required), event_id (required), name. Returns: object

create_eventB

Create a new Luma event.

Args:
    name: The title of the event
    start_at: Start time in ISO 8601 format (e.g., "2024-12-31T23:59:00Z")
    location: Event location with place_id (Google Maps) and optional description
    end_at: End time in ISO 8601 format (optional)
    description_md: Event description in Markdown format (optional)
    cover_url: URL for the event cover image (optional)

Returns:
    The created event data or an error message

Inputs: name (required), location (required), start_at (required), end_at, +2 more. Returns: object

get_all_past_guestsA

Get all unique guests from all past events.

Returns:
    De-duplicated list of Guest objects (by email)

Inputs: no named parameters. Returns: result

get_eventA

Get details about a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")

Returns:
    The event data or an error message

Inputs: event_id (required). Returns: object

get_guestA

Get a specific guest for a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")
    guest_id: The unique identifier of the guest

Returns:
    Guest data or an error message

Inputs: event_id (required), guest_id (required). Returns: object

get_guestsB

Get all guests for a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")

Returns:
    List of guests or an error message

Inputs: event_id (required). Returns: object

list_eventsA

List all events for the default calendar.

Returns:
    List of events or an error message

Inputs: no named parameters. Returns: object

send_invitesB

Send invites to guests for a Luma event.

Args:
    event_id: The unique identifier of the event (e.g., "evt-ABC123")
    guests: List of Guest objects with email (required) and name (optional)

Returns:
    Result of sending invites or an error message

Inputs: guests (required), event_id (required). Returns: object

update_eventA

Update an existing Luma event.

Args:
    event_id: The unique identifier of the event to update (api_id)
    name: New title for the event (optional)
    description_md: New description in Markdown format for the event (optional)
    start_at: New start time in ISO 8601 format (optional)
    end_at: New end time in ISO 8601 format (optional)
    cover_url: New URL for the event cover image (optional)
    location: New event location (optional)

Returns:
    The updated event data or an error message

Inputs: event_id (required), name, end_at, location, +3 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: events (list/get/create/update), guests (get/get_all/get for event), hosts (add), and invitations (send). No two tools appear to do the same thing, and singular/plural guest tools are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as list_events, create_event, update_event, and send_invites. The naming style is uniform and predictable across the entire server.

    Tool Count5/5

    Nine tools is a well-scoped count for an event management server. Each tool covers a meaningful operation without unnecessary redundancy or bloat.

    Completeness4/5

    The tool surface covers the core event lifecycle (create, read, update, list) and guest-related workflows (view guests, send invites, add hosts). Minor gaps exist, such as no delete/cancel event or remove host, but these are workarounds rather than dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers