Skip to main content
Glama
montaguegabe

luma-events-mcp

by montaguegabe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LUMA_API_KEYYesYour Luma API key (requires Luma Plus subscription)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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
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
get_all_past_guestsA

Get all unique guests from all past events.

Returns:
    De-duplicated list of Guest objects (by email)
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
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
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
list_eventsA

List all events for the default calendar.

Returns:
    List of events or an error message
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
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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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
ResponsivenessNo issues

Resources