A
licenseA
qualityD
maintenanceDiscovers events from Luma's public feed and subscribed calendars, with distance filtering, category search, and ICS export. No API key required for basic discovery.
4
MIT
better_luma
Related Servers
Alternatives to better_luma
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to view Partiful events, RSVPs, hosted events, mutual connections, and user profiles via a community-built MCP server.413 npm1MIT
- FlicenseBqualityDmaintenanceEnables access to Network School Luma calendar events through Claude Desktop. Allows users to view today's events, search upcoming events, and register for events directly with their contact information.517 npm-
- AlicenseNot gradedqualityBmaintenanceEnables read-only discovery and planning of San Francisco Tech Week events, including searching by hosts, topics, dates, and building itineraries or calendar drafts.MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Eventbrite API to provide AI-assisted event management capabilities for viewing events, tracking attendees, and generating analytics reports.4 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search and access public calendar data, supporting iCal, CalDAV, and Google Calendar sources with event search, details, and availability checks.-
TDQS
A3.6/5.0
Scored across 10 tools
Disambiguation3/5
Most tools target distinct actions, but some overlap exists: list_events and scrape_city both collect events, get_event_guests and scrape_city both collect attendees, and list_my_luma_events overlaps with verify_luma_host in checking host status. The descriptions reduce ambiguity but the boundaries are not always crisp.
Naming Consistency4/5
The naming pattern is mostly consistent verb_noun snake_case, e.g. list_events, get_event, search_events, verify_luma_host. The lone 'health' tool breaks the pattern by not using a verb, though it is still understandable.
Tool Count5/5
Ten tools is a well-scoped count for an event aggregation/read-only API. Each tool covers a distinct aspect of the domain without unnecessary bloat or obvious redundancy.
Completeness4/5
The toolset covers the core read-only workflow: event types, cities, event listing/search/detail, guests, city scraping, and authenticated user event queries. Minor gaps exist such as no explicit platform-list tool or direct attendee export beyond guests, but agents can mostly accomplish the intended tasks.
Maintenance
ActivityMaintained
ResponsivenessNo issues