F
licenseA
qualityD
maintenanceAn MCP server for the Luma Events API that enables creating, updating, and managing events and guests.
9
6
-
Luma Events MCP Server
by Blackie360
Related Servers
Alternatives to Luma Events MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for managing Luma events, including creating and updating events, setting ticket types and prices, issuing coupon codes, listing RSVPs, and sending emails to attendees, with a safety-first draft+confirm pattern.16MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for managing events on Meetup.com and Luma via AI assistants like Claude.2-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that dynamically sources global technology events, communities, and niche networking mixers from Luma, Eventbrite, Meetup, and fallback search sources, enabling event discovery and community finding via natural language.-
- FlicenseNot gradedqualityDmaintenanceMCP server for eventos event management platform, enabling AI assistants to manage events and tickets via API integration. Supports authentication, ticket CRUD operations, and listing with pagination.1-
- FlicenseAqualityDmaintenanceA simple MCP server for event scheduling and automation.12-
TDQS
A3.7/5.0
Scored across 23 tools
Disambiguation4/5
Most tools map to a distinct resource/action combination, but add_guests, send_invites, and invite_guests_from_event occupy similar invite/registration territory, and approve_waitlisted_guests overlaps with update_guest_status at the bulk level. Detailed descriptions help, but an agent could still hesitate between these related actions.
Naming Consistency4/5
Nearly all tools follow a snake_case verb_noun pattern (create_event, delete_ticket_type, update_guest_status), with resource-consistent CRUD verbs. Minor deviations like registration_summary and synonym variation (add vs create, remove vs delete) keep it from being perfect.
Tool Count3/5
23 tools is at the high end for an MCP server and will feel heavy to navigate, though the count is justified by distinct subdomains (events, guests, hosts, ticket types, invites). It is not excessive enough to be chaotic, but it exceeds the ideal 3-15 range.
Completeness4/5
Events, hosts, and ticket types have full CRUD/lifecycle coverage, and guests have add/list/get/update operations with bulk approval. Gaps like direct guest removal and guest check-in are noticeable but can be partially worked around through status/ticket updates and registration_summary.
Maintenance
ActivityMaintained
ResponsivenessNo issues