Skip to main content
Glama
adelaidasofia

luma-mcp

by adelaidasofia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to luma-mcp

No user-submitted related servers found.

    Related Servers

    • Luma Events MCP Server

      Blackie360
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for managing Luma events, including listing, creating, updating events and guest registrations with privacy-conscious summaries.
      23
      26 npm
      2
      MIT

    • pretix-agent-mcp

      bitcoinaustria
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to safely administer pretix events, with capability controls, PII masking, and approval-gated destructive operations.
      MIT

    • MCP Global Events

      Nickfx9
      F
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a distinct purpose: health check, event CRUD with draft/confirm pattern, ticket types, coupons, guests, and email blasts. No overlapping functionality, and descriptions clearly differentiate operations.

    Naming Consistency5/5

    All tools follow a consistent 'luma_verb_noun' pattern with underscores. Verbs are intuitive (create, update, list, get, cancel, send) and nouns describe the resource (event, ticket_type, coupon, guest). Very predictable.

    Tool Count5/5

    16 tools is a well-scoped set for an event management API. It covers draft/confirm workflows, listing, and auxiliary operations without unnecessary bloat or missing essentials.

    Completeness4/5

    Core event lifecycle (create, update, get, list, cancel drafts) is covered, plus ticket types, coupons, guests, and email sending. Missing: ability to delete confirmed events or update ticket types/coupons after creation. Minor gaps but overall comprehensive.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources