Skip to main content
Glama
mrh-is

partiful-mcp

by mrh-is

Related Servers

Alternatives to partiful-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse public event listings from explore pages and fetch full detail for a single event — titles, descriptions, times, locations, host display names, and aggregate RSVP counts — across eight supported city regions. Keyless and read-only, with no guest lists, contact info, or authentication required.
      18 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search upcoming public events and group topic categories by keyword, city, or group slug, and to retrieve full details for individual events and groups, keylessly and without touching attendee or member data.
      175 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only tools for discovering, searching, and browsing events from Luma, Posh, and Partiful platforms, including event details and guest lists, with optional authenticated access to a user's Luma events.
      10
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for automating Meetup event tracking with an AI agent. It equips the agent with tools to browse Meetup.com, detect new events since the last known record, and return structured event data.
      200 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 41 tools

    Disambiguation3/5

    Many tools have overlapping purposes, especially the 8+ event-list getters (get_my_rsvps, get_my_upcoming_events_for_home_page, get_my_past_events_for_home_page, get_published_events, get_discoverable_events, get_my_saved_events, get_my_followed_events). Detailed descriptions help disambiguate, but the sheer number of similar-sounding tools makes misselection likely.

    Naming Consistency5/5

    All 40 read tools follow the get_<noun> pattern, and the sole write tool uses mark_<noun>_as_<state>. The naming is uniform and predictable, with no mixed conventions.

    Tool Count2/5

    41 tools is excessive for the apparent scope. Many tools are extremely granular (ticket-related tools split across 5 separate getters, event lists split across 8 getters). The count could likely be reduced to 15-20 useful tools without losing functionality.

    Completeness1/5

    The tool surface is almost entirely read-only. There are no create/update/delete operations for events, contacts, or communities, no RSVP actions, no invite sending, and no comment posting. Only one write action exists (mark notifications read), which is a severe gap for an event-management platform.

    Maintenance

    ActivityActive
    ResponsivenessNo issues